Repository navigation
fix(pnpm): download the native binary from the configured registry #102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: garnet/routing-base
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "pacquet": patch | ||
| --- | ||
|
|
||
| When the `pnpm` package has to download its native binary on first run, it now uses the registry and credentials from `.npmrc` and from the `npm_config_registry` and `pnpm_config_registry` environment variables. `COREPACK_NPM_REGISTRY` still takes precedence. A project `.npmrc` is not read when `COREPACK_INTEGRITY_KEYS` turns off the signature check [#16655](https://github.com/pnpm/pnpm/issues/16655). |
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔴 Nested projects lose their registry From a subdirectory of a standalone project, (Refers to this code) Learn moreThe wrapper runs before the native CLI can load its configuration. The CLI finds a project's local prefix using package markers before reading Example: Recommended fix: Use the CLI's local-prefix markers for standalone projects while retaining workspace-root precedence where a workspace file exists. Test a nested working directory. Was this helpful? React with 👍 or 👎 to provide feedback. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔴 Environment-only registry authentication fails When registry credentials exist only in URL-scoped environment variables, (Refers to this code) Learn moreThe native CLI accepts URL-scoped Example: Recommended fix: Include URL-scoped credential environment variables in Was this helpful? React with 👍 or 👎 to provide feedback. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔍 Saved login credentials are unavailable during bootstrap A private registry configured through (Refers to this code) Was this helpful? React with 👍 or 👎 to provide feedback. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔍 No Execution Profile for current head The PR description has no Execution Profile for (Refers to this code) Was this helpful? React with 👍 or 👎 to provide feedback. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟥 Project registry can claim trusted credentials When a project selects a registry matching a user-level credential scope, (Refers to this code) Was this helpful? React with 👍 or 👎 to provide feedback. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Environment registry override loses to project config
When a project sets
@pnpm:registry,registryAccessignores an explicit registry environment override. First-run downloads use the project registry even when the operator supplies another registry.(Refers to this code)
Was this helpful? React with 👍 or 👎 to provide feedback.