Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#1,044 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
78/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
node.js, playwright, typescript
Domaine
developer-experience, tooling

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
TypeScript
Étoiles
481
Forks
45
Merge moyen
1 j 9 h
PR mergées (30 j)
86

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ai-driven-dev/framework

Toutes les issues de ai-driven-dev/framework

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.