You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'm trying to install one package as a dependency for another one. Both packages are managed by Rush, but are not published. I'm getting an ERR_PNPM_FETCH_404 error, because pnpm is trying to fetch it from the registry for some reason.
Repro steps
Create new Rush project.
Add two new packages to it (list them in rush.json).
Try to link them together by mentioning the package name of one package as a dependency for another one in package.json.
Run rush update.
Expected result:
Dependency should be successfully installed by linking the local package.
Actual result:
I'm getting an ERR_PNPM_FETCH_404 error.
Details
Nothing I can think of.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
Question
Answer
@microsoft/rush globally installed version?
5.83.4
rushVersion from rush.json?
5.83.4
useWorkspaces from rush.json?
undefined
Operating system?
Ubuntu 22.04.1 LTS
Would you consider contributing a PR?
No
Node.js version (node -v)?
v18.12.1
The text was updated successfully, but these errors were encountered:
Summary
Hello! I'm trying to install one package as a dependency for another one. Both packages are managed by Rush, but are not published. I'm getting an
ERR_PNPM_FETCH_404
error, because pnpm is trying to fetch it from the registry for some reason.Repro steps
rush.json
).package.json
.rush update
.Expected result:
Dependency should be successfully installed by linking the local package.
Actual result:
I'm getting an
ERR_PNPM_FETCH_404
error.Details
Nothing I can think of.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/rush
globally installed version?5.83.4
rushVersion
from rush.json?5.83.4
useWorkspaces
from rush.json?undefined
Ubuntu 22.04.1 LTS
node -v
)?v18.12.1
The text was updated successfully, but these errors were encountered: