fix: work around pnpm v11 ERR_PNPM_MISSING_TIME with sfw-free proxy#257
Closed
John-David Dalton (jdalton) wants to merge 2 commits intomainfrom
Closed
fix: work around pnpm v11 ERR_PNPM_MISSING_TIME with sfw-free proxy#257John-David Dalton (jdalton) wants to merge 2 commits intomainfrom
John-David Dalton (jdalton) wants to merge 2 commits intomainfrom
Conversation
John-David Dalton (jdalton)
force-pushed
the
fix/pnpm-v11-resolution-mode
branch
4 times, most recently
from
c62bdf5 to
8fb8e13
Compare
- Add overrides as direct dependencies (not pnpm.overrides) to work around pnpm v11 RC regression where npm: alias overrides are ignored for subdeps - Add resolution-mode=highest (SFW proxy strips time field from registry metadata) - Add confirmModulesPurge=false (prevent interactive prompts) - Add block-exotic-subdeps=false for test installs (third-party git deps) - Add strict-dep-builds=false for test installs (third-party build scripts) - Reduce install concurrency to 3 (pnpm v11 store corruption at high parallelism) - Add is-unicode-supported to allowed failures (pnpm/pnpm#11238) - Add is-unicode-supported unit tests (ported 1:1 from upstream v2.1.0)
John-David Dalton (jdalton)
force-pushed
the
fix/pnpm-v11-resolution-mode
branch
from
8fb8e13 to
329f9a4
Compare
John-David Dalton (jdalton)
force-pushed
the
main
branch
from
ef17955 to
aa242b7
Compare
Collaborator
Author
|
Changes pushed directly to main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--config.resolution-mode=highestto pnpm install flags used by the npm package test script, working around sfw-free proxy not forwarding the"time"field in registry metadatatest/npm/.npmrcsettings totest/npm/pnpm-workspace.yaml(pnpm v11 only reads auth/registry from.npmrc)test/npm/.npmrcContext
pnpm v11 changed the default
resolution-modeto"time-based", which requires the"time"field in npm registry metadata. The sfw-free proxy strips or omits this field, causingERR_PNPM_MISSING_TIMEfor 104/109 test package installs in CI.Test plan
pnpm installintest/npm/still works locally