JacobLinCool / JacobLinCool/fetch-impl

Dependency Dashboard

Offen
#1 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Vorherrschende Sprache
TypeScript
Sterne
2
Forks
1
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/JacobLinCool/fetch-impl).

## Config Migration Needed

- [ ] Select this checkbox to let Renovate create an automated Config Migration PR.

## Rate-Limited

The following updates are currently rate-limited. To force their creation now, click on a checkbox below.

- [ ] chore(deps): update dependency husky to v9.1.7
- [ ] chore(deps): update dependency tsup to v8.5.1
- [ ] chore(deps): update dependency typedoc to ^0.28.0
- [ ] chore(deps): update dependency typescript to v5.9.3
- [ ] chore(deps): update actions/checkout action to v7
- [ ] chore(deps): update actions/configure-pages action to v6
- [ ] chore(deps): update actions/deploy-pages action to v5
- [ ] chore(deps): update actions/upload-pages-artifact action to v5
- [ ] chore(deps): update changesets/action action to v2
- [ ] chore(deps): update dependency @changesets/changelog-github to v1
- [ ] chore(deps): update dependency @changesets/cli to v3
- [ ] chore(deps): update dependency @types/node to v24
- [ ] chore(deps): update dependency lint-staged to v17
- [ ] chore(deps): update dependency prettier-plugin-organize-imports to v4
- [ ] chore(deps): update dependency typescript to v7
- [ ] chore(deps): update pnpm to v12
- [ ] chore(deps): update pnpm/action-setup action to v6
- [ ] chore(deps): update vitest monorepo to v5 (`@vitest/coverage-v8`, `vitest`)
- [ ] 🔐 **Create all rate-limited PRs at once** 🔐

## Open

The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.

- [ ] [chore(deps): update dependency serve to v14.2.6](../pull/12)
- [ ] [chore(deps): update dependency @changesets/changelog-github to ^0.7.0](../pull/22)
- [ ] [chore(deps): update dependency @changesets/cli to v2.31.1](../pull/16)
- [ ] [chore(deps): update dependency @types/node to v20.19.43](../pull/15)
- [ ] [chore(deps): update dependency debug to v4.4.3](../pull/18) (`debug`, `@types/debug`)
- [ ] [chore(deps): update dependency lint-staged to v15.5.2](../pull/17)
- [ ] [chore(deps): update dependency prettier to v3.9.6](../pull/19)
- [ ] [chore(deps): update dependency tsx to v4.23.13](../pull/14)
- [ ] [chore(deps): update pnpm to v9.15.9](../pull/11)
- [ ] [chore(deps): update vitest monorepo to v1.6.1](../pull/13) (`@vitest/coverage-v8`, `vitest`)
- [ ] **Click on this checkbox to rebase all open PRs at once**

## Detected Dependencies

github-actions (3)

.github/workflows/docs.yml (5)

- `actions/checkout v4` → [Updates: `v7`]
- `pnpm/action-setup v3` → [Updates: `v6`]
- `actions/configure-pages v4` → [Updates: `v6`]
- `actions/upload-pages-artifact v3` → [Updates: `v5`]
- `actions/deploy-pages v4` → [Updates: `v5`]

.github/workflows/release.yml (3)

- `actions/checkout v4` → [Updates: `v7`]
- `pnpm/action-setup v3` → [Updates: `v6`]
- `changesets/action v1` → [Updates: `v2.1.2`]

.github/workflows/test.yml (2)

- `actions/checkout v4` → [Updates: `v7`]
- `pnpm/action-setup v3` → [Updates: `v6`]

npm (6)

package.json (15)

- `@changesets/changelog-github ^0.5.0` → [Updates: `^0.7.0`, `^1.0.0`]
- `@changesets/cli ^2.27.1` → [Updates: `^2.27.1`, `^3.0.0`]
- `@types/node ^20.12.7` → [Updates: `^20.12.7`, `^24.0.0`]
- `@vitest/coverage-v8 ^1.5.0` → [Updates: `^1.5.0`, `^5.0.0`]
- `husky ^9.0.11` → [Updates: `^9.0.11`]
- `lint-staged ^15.2.2` → [Updates: `^15.2.2`, `^17.0.0`]
- `prettier ^3.2.5` → [Updates: `^3.2.5`]
- `prettier-plugin-organize-imports ^3.2.4` → [Updates: `^4.0.0`]
- `serve ^14.2.1` → [Updates: `^14.2.1`]
- `tsup ^8.0.2` → [Updates: `^8.0.2`]
- `tsx ^4.7.2` → [Updates: `^4.7.2`]
- `typedoc ^0.25.13` → [Updates: `^0.28.0`]
- `typescript ^5.4.5` → [Updates: `^5.4.5`, `^7.0.0`]
- `vitest ^1.5.0` → [Updates: `^1.5.0`, `^5.0.0`]
- `pnpm 9.0.1` → [Updates: `9.15.9`, `12.4.1`]

packages/cross-fetch/package.json (5)

- `@types/node ^20.12.7` → [Updates: `^20.12.7`, `^24.0.0`]
- `tsup ^8.0.2` → [Updates: `^8.0.2`]
- `typedoc ^0.25.13` → [Updates: `^0.28.0`]
- `typescript ^5.4.5` → [Updates: `^5.4.5`, `^7.0.0`]
- `cross-fetch *`

packages/fetcher/package.json (4)

- `@types/node ^20.12.7` → [Updates: `^20.12.7`, `^24.0.0`]
- `tsup ^8.0.2` → [Updates: `^8.0.2`]
- `typedoc ^0.25.13` → [Updates: `^0.28.0`]
- `typescript ^5.4.5` → [Updates: `^5.4.5`, `^7.0.0`]

packages/playwright/package.json (8)

- `debug ^4.3.4` → [Updates: `^4.3.4`]
- `@types/debug ^4.1.12` → [Updates: `^4.1.12`]
- `@types/node ^20.12.7` → [Updates: `^20.12.7`, `^24.0.0`]
- `tsup ^8.0.2` → [Updates: `^8.0.2`]
- `typedoc ^0.25.13` → [Updates: `^0.28.0`]
- `typescript ^5.4.5` → [Updates: `^5.4.5`, `^7.0.0`]
- `playwright *`
- `playwright-core *`

packages/puppeteer/package.json (8)

- `debug ^4.3.4` → [Updates: `^4.3.4`]
- `@types/debug ^4.1.12` → [Updates: `^4.1.12`]
- `@types/node ^20.12.7` → [Updates: `^20.12.7`, `^24.0.0`]
- `tsup ^8.0.2` → [Updates: `^8.0.2`]
- `typedoc ^0.25.13` → [Updates: `^0.28.0`]
- `typescript ^5.4.5` → [Updates: `^5.4.5`, `^7.0.0`]
- `puppeteer *`
- `puppeteer-core *`

pnpm-workspace.yaml

---

- [ ] Check this box to trigger a request for Renovate to run again on this repository

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne mit package.json, den Paketmanifesten unter packages/ und .github/workflows/docs.yml, release.yml und test.yml, um die aufgeführten Renovate-Aktualisierungen zu verstehen. Anhand der Kontrollkästchen im Dashboard und der verknüpften Pull Requests lässt sich erkennen, welche Abhängigkeitsarbeiten bereits automatisiert sind; als erledigt würde gelten, eine bestimmte noch ausstehende Aktualisierung zu bearbeiten und zu bestätigen, dass die betroffenen Prüfungen erfolgreich sind.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
github-actions, playwright, typescript
Bereich
build-system, ci-cd, devops
Issue-Typ
Refactoring
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
20/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.