fix(ci): translate tarsync yarn resolutions to pnpm overrides#2019
Merged
Tobbe merged 3 commits intoJul 1, 2026
Merged
Conversation
pnpm ignores yarn's `resolutions` field, so after tarsync populates it with local tarball paths, `pnpm install` fetched framework packages from the npm registry instead. The published canary of @cedarjs/project-config predates the web/index.html move (cedarjs#1799) and still resolves html to web/src/index.html, causing Vite to fail with "Could not resolve entry module src/index.html" on every pnpm smoke test run. Fix: read the tarsync-added resolutions and emit them as pnpm overrides (with file: prefix) in pnpm-workspace.yaml so pnpm install uses the local tarballs. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for cedarjs canceled.
|
Contributor
Greptile SummaryThis PR makes pnpm smoke-test setup use the local framework tarballs written by tarsync. The main changes are:
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (3): Last reviewed commit: "formatting and refactoring" | Re-trigger Greptile |
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx run-many -t build:pack --exclude create-ceda... |
✅ Succeeded | 7s | View ↗ |
nx run-many -t build |
✅ Succeeded | 6s | View ↗ |
nx run-many -t test --minWorkers=1 --maxWorkers=4 |
✅ Succeeded | 6s | View ↗ |
nx run-many -t test:types |
✅ Succeeded | 7s | View ↗ |
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗
☁️ Nx Cloud last updated this comment at 2026-07-01 04:02:48 UTC
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
In YAML single-quoted scalars a literal single-quote must be doubled. Package names like @cedarjs/foo never contain single quotes, but the tarball path could on unusual runner configs. Escape both to be safe. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
2 participants
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
• Root cause: pnpm ignores yarn's
resolutionsfield. Aftertarsyncruns and writes local tarball paths intopackage.json'sresolutions,pnpm installignores those and fetches@cedarjs/project-config@4.2.0from the npm registry. The published canary predates PR #1799 (which movedindex.htmlfromweb/src/toweb/) and still resolvespaths.web.htmltoweb/src/index.html.• Symptom: Every pnpm smoke test since 2026-06-26 fails with
Could not resolve entry module "src/index.html"— 5 consecutive daily failures.• Fix: After tarsync runs, read its yarn
resolutionsentries that point to local.tgzfiles and emit them as pnpm overrides (withfile:prefix) inpnpm-workspace.yaml, sopnpm installuses the local tarballs instead of the stale registry canary.Test plan
🤖 Generated with Claude Code