-
Notifications
You must be signed in to change notification settings - Fork 595
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
[rush] "rush update" error when adding new project to rush.json #1418
Comments
@sachinjoseph, this looks like a regression from one of your recent PNPM bugfixes. Can you take a look at this? |
Looking into it |
sachinjoseph
added a commit
that referenced
this issue
Jul 26, 2019
…e PNPM shrinkwrap. This fixes the regression #1418.
@ScottHysom Can you verify with Rush 5.11.0? |
I have confirmed this issue has been resolved with 5.11.0. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a feature or a bug?
Please describe the actual behavior.
With rush version 5.10.3 and pnpm version 3.6.0, users can no longer add a new project to their
rush.json
and runrush update
. Instead,rush update
results in this error:ERROR: Cannot get dependency key for temp project: @rush-temp/new-project
A simple repro can be found at https://github.com/ScottHysom/rush-issue-add-project. See the README.md for simple repro steps.
To work around this issue, a user must manually change the
pnpm-lock.yaml
and add the following line under the topdependencies
key:'@rush-temp/new-project': 'file:path-to-project/new-project.tgz'
What is the expected behavior?
rush update
succeeds in updating the pnpm lock file without manual intervention.If this is a bug, please provide the tool version, Node.js version, and OS.
The text was updated successfully, but these errors were encountered: