Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

fix(framework): replace hardcoded npx with a <runner> placeholder in skills

Offen
  • Stimmt etwas nicht?
#1,044 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
78/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
node.js, playwright, typescript
Bereich
developer-experience, tooling

Rechercherichtung

Start with the three listed files: the Playwright CLI reference, the acceptance QA prerequisites, and the MCP installation recipe. Find each npx use, add the runner convention in each file, and update prerequisite detection to accept an available alternative runner. Validate using an alternative runner; done means no hardcoded npx remains in shipped skills and the QA flow produces its evidence videos.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Summary: Several shipped skills hardcode npx in their commands; users on alternative Node runners (pnpx, bunx, nubx, pnpm dlx, …) cannot run them.

🌟 Objective / Problem

Skills under plugins/ invoke npx directly. On machines where npx is not installed — increasingly common with alternative Node toolchains — the affected skills fail. Example: 01-acceptance-qa requires resolving npx as a prerequisite, so the whole QA flow is blocked on such machines.

Affected locations (found by grepping the shipped plugins for npx):

  • plugins/aidd-qa/skills/01-acceptance-qa/references/interface-browser-playwright-cli.md — 6 occurrences, e.g. npx --yes @playwright/[email protected] -s=qa-<run-id> <command>
  • plugins/aidd-qa/skills/01-acceptance-qa/actions/02-prerequisites.md — 2 occurrences (the check resolves npx and runs npx --yes @playwright/[email protected] --version)
  • plugins/aidd-context/skills/12-cook/assets/recipes/mcp-installation.md — 1 occurrence (npx playwright)

🛠️ Proposed Solution

  1. Replace every hardcoded npx in skill content with a <runner> placeholder, meaning "any package runner: npx, pnpx, bunx, nubx, pnpm dlx, …".
  2. State the convention once at the top of each affected file, e.g.: <runner> is your package runner: npx, pnpx, bunx, nubx, …
  3. In the 01-acceptance-qa prerequisites check, resolve whichever runner is available instead of requiring npx specifically.

🔍 Context / Technical Constraints (Optional)

  • Out of scope: historical records under aidd_docs/tasks/ and the CLI install docs (cli/README.md), where npx @ai-driven-dev/cli@latest setup is the canonical npm install path.

🙏 QA

Validation must be done with an alternative package runner (pnpx, bunx, nubx, pnpm dlx, …) — not with npm/npx.

  • No hardcoded npx remains in the shipped skills under plugins/
  • Each file that uses <runner> defines the placeholder once
  • 01-acceptance-qa prerequisites pass on a machine where npx is absent, resolving an alternative runner instead
  • The 01-acceptance-qa flow runs end to end through an alternative runner (pnpx, bunx or nubx) and produces its evidence videos
Vorherrschende Sprache
TypeScript
Sterne
481
Forks
45
Ø Merge
1 T. 2 Std.
Gemergte PRs (30 T.)
77

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ai-driven-dev/framework

Alle Issues in ai-driven-dev/framework

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

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