Skip to content

fix(cli): respect npm registry config in update check - #484

Merged
Pavel Feldman (pavelfeldman) merged 2 commits into
microsoft:mainfrom
pavelfeldman:fix-478
Oct 19, 2026
Merged

Pavel Feldman (pavelfeldman) merged 2 commits into
microsoft:mainfrom
pavelfeldman:fix-478

Conversation

@pavelfeldman

@pavelfeldman Pavel Feldman (pavelfeldman) commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Update check now runs npm view @playwright/cli version instead of fetching registry.npmjs.org, so npm resolves the registry (incl. @playwright:registry), proxy and auth. Only on open, attach, list, install and install-browser to contain the npm startup cost; failures and the 1.5s timeout stay silent.

Fixes #478

Comment thread playwright-cli.js Outdated
Comment thread tests/integration.spec.ts
expect(npmRegistry.requests).toEqual(['/@playwright%2fcli']);
});

test('update check on install does not warn about the skills being installed', async ({ npmRegistry }) => {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we reduce number of the new tests?

@pavelfeldman
Pavel Feldman (pavelfeldman) merged commit b1a5903 into microsoft:main Oct 19, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update checks should respect npm registry configuration to avoid Windows Security warnings in enterprise environments

2 participants