Pnpm migration#3366
Conversation
|
Here's what it looks like for migrating to pnpm |
|
@jeremymeng could you update the ci.yaml/release.yaml? I think those have references to the rush scripts. |
@qiaozha I have updated files under .scripts and no longer see any references of "rush". I don't know for sure though whether replacing them with |
This reverts commit 71e6eb3.
|
Looks that CI checks were all passing. I don't know whether we have other places that is not in this repo where we still build using |
| "pnpm": ">=10.12.1" | ||
| }, | ||
| "pnpm": { | ||
| "overrides": {}, |
There was a problem hiding this comment.
pls check if we need to add this global overrides.
There was a problem hiding this comment.
It's empty and does not do anything currently, but provide a place to add overrides in the future if needed.
There was a problem hiding this comment.
Yes we have this requirement in nightly ci to upgrade to latest dev globally. JiaoDi will help verify if the global overrides work in nightly ci.
| workingDirectory: $(Build.SourcesDirectory)/packages/typespec-ts | ||
| - script: | | ||
| export TAR_NAME=$(node ../../common/scripts/install-run-rush-pnpm.js pack -q) | ||
| export TAR_NAME=$(pnpm pack -q) |
There was a problem hiding this comment.
This will lead to invalid tar name so we can't release.
4 participants
No description provided.