-
Notifications
You must be signed in to change notification settings - Fork 294
Open
Description
Bug description
The README.md and skills/playwright-cli/SKILL.md reference npx playwright-cli in the "Installation" / "Local installation" sections. However, the npm package name is @playwright/cli (scoped), while playwright-cli on npm is a deprecated old package:
$ npm view playwright-cli
playwright-cli@0.262.0 | Apache-2.0
DEPRECATED ⚠️ - This package is deprecated, use @playwright/cli instead.
This means:
npx playwright-cli(without--no-install) will download and run the deprecated package, not the current@playwright/clinpx -y playwright-cli(commonly used by agents for non-interactive fallback) silently installs the wrong package
Affected locations
README.md (Installation section):
try a local version via `npx playwright-cli`:
...
When local version is available, use `npx playwright-cli` in all commands.
skills/playwright-cli/SKILL.md (Installation section):
Same text as README.
Suggested fix
Replace npx playwright-cli with npx @playwright/cli in prose and examples where the intent is to run via npx (auto-download). The npx --no-install playwright-cli --version check is fine since it only resolves locally installed binaries.
For example:
-When local version is available, use `npx playwright-cli` in all commands.
+When local version is available, use `npx @playwright/cli` in all commands.And for the global install instruction, it's already correct: npm install -g @playwright/cli@latest.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels