-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[BUG] Tracker idealTree inflate error with workspaces after failed install #3496
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
Comments
cinderblock
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
labels
Jul 1, 2021
Downgrading to 7.17 seems to avoid this issue but I am not sure where to begin troubleshooting |
I use npm 7.20.5 and meet this problem too. |
ivomurrell
added a commit
to Financial-Times/dotcom-tool-kit
that referenced
this issue
Sep 8, 2021
Running into issues where installing in a package throws the error 'Tracker "idealTree:inflate:" already exists'. The GitHub issue suggests that the best fix for now is to use npm 7.17: npm/cli#3496
ivomurrell
added a commit
to Financial-Times/dotcom-tool-kit
that referenced
this issue
Sep 23, 2021
Running into issues where installing in a package throws the error 'Tracker "idealTree:inflate:" already exists'. The GitHub issue suggests that the best fix for now is to use npm 7.17: npm/cli#3496
ivomurrell
added a commit
to Financial-Times/dotcom-tool-kit
that referenced
this issue
Sep 29, 2021
Running into issues where installing in a package throws the error 'Tracker "idealTree:inflate:" already exists'. The GitHub issue suggests that the best fix for now is to use npm 7.17: npm/cli#3496
ivomurrell
added a commit
to Financial-Times/dotcom-tool-kit
that referenced
this issue
Oct 5, 2021
Running into issues where installing in a package throws the error 'Tracker "idealTree:inflate:" already exists'. The GitHub issue suggests that the best fix for now is to use npm 7.17: npm/cli#3496
The idealTree error was fixed in #4300 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
Is there an existing issue for this?
Current Behavior
I have a large existing project that I'm trying to move to Npm 7 and workspaces. (I'm trying to cut it down to something I can share, but that's a lot more work than I hope is necessary.)
The project has 3 "sub-projects" that historically have been "managed" with a
package.json#script
like:yarn --cwd sub-project
(I'm also moving away from Yarn).These sub-packages already had
package.json
files with large lists of dependencies.First I tried
npm init -w ui -w daemon -w deploy
but that just regenerated my sub-packages'package.json
files.Then I realized all that was needed was to add
package.json#worksapces
array of the 3 folder names.So I cleared all my
node_modules
folders and all thepackage-lock.json
files (I was doing a bunch of updates withncu
as well).Then I run
npm install --legacy-peer-deps
because I have somepeerDependencies
that apparently need it.However there is always an error.
One of those errors is a encoding/code page issue (running in Windows Terminal PowerShell):
Full log: 2021-07-01T20_43_41_461Z-debug.log
If I run
npm install --legacy-peer-deps
again, it usually fails much faster with a simpler message:Full log: 2021-07-01T20_17_00_868Z-debug.log
I used to be able to wipe away my
node_modules
folder for this error to temporarily go away (only to return on re-run).Testing again to generate full accurate logs, now the
node_modules
folder is cleared away on error...Expected Behavior
Steps To Reproduce
peerDependencies
)npm install --legacy-peer-deps
Environment
14.17.1
node
as dependency:16.4.0
7.19.1
The text was updated successfully, but these errors were encountered: