fix: respect npm_config_registry for update checks

[Will-hxw]

Summary

Use npm_config_registry environment variable for npm registry URL in update checks, instead of hardcoding registry.npmjs.org.

Fix

check-latest-version.ts now respects the user's npm registry configuration. This helps users behind corporate proxies or using private registries (e.g., JFrog Artifactory).

When npm_config_registry is not set, falls back to the default public registry.

Validation

• npm run build passes
• npm test passes

Fixes #1943

[Will-hxw]

Hi @coty @precision , sorry to bother you. This PR has been open for a while, so I wanted to kindly check whether you might have time to review it or let me know if any changes are needed.I’m happy to make adjustments if required. Thanks!

[wolfib]

Thanks!

As discussed in here, this does not solve the case where the DevTools CLI is called directly. @mathiasbynens WDYT? Should the suggestion from here be added?

[mathiasbynens]

Thanks!

As discussed in here, this does not solve the case where the DevTools CLI is called directly. @mathiasbynens WDYT? Should the suggestion from here be added?

Yeah, if we need to support this then let’s do it properly and support all use cases, not just those through npx or npm run.

The “proper” way to do it would be to use @npmcli/config, but this comes at the cost of a dependency.

[Will-hxw]

Thanks for the suggestion. Adding @npmcli/config as a dependency would indeed handle all cases properly, but you're right that it introduces a new dependency.

Given the PR is already behind and this would be a meaningful scope expansion, I think it makes sense to treat this as a follow-up PR rather than growing this one further. Would you be okay with merging the current fix as-is (for the npx/npm case) and addressing the direct-CLI case in a separate PR with the proper implementation?

[Will-hxw]

@wolfib Thanks for the follow-up! The plan is to merge the current fix for the npx/npm case, then address the direct-CLI scenario in a follow-up with the proper @npmcli/config implementation. This keeps this PR focused and lets us do the full solution justice. I'll open a new issue to track the direct-CLI work after this merges.