-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Dependency issues when building on Ubuntu x64 #4385
Comments
It also gets angry if you run |
We don't support most of what you wrote about, such as direct Lerna commands or running |
The reason I posted this issue is that I followed the instructions in As for running direct Again, I followed the instructions in I see that you removed the "bug" label. While this issue isn't a bug with the built software, it is a bug with the build script. It is, indeed, actually a bug, which you will see if you more closely reread what I wrote. |
Oh, look, I'm getting build errors on my Mac, as well:
[extraneous output removed]
Huh! If I go into the first log file, this is what I see:
If I go into the second log file, this is what I see:
Googling "@npmcli/promise-spawn/index.js:64:27", I get this Stack Overflow result, which suggests the problem is a typo somewhere in |
Incidentally, while |
What's the complete output of
You've installed Lerna globally and ran that, so you're most likely using a version that's different from the one that comes with the monorepo. You've also installed it with sudo, which you shouldn't as it will cause various permission issues. If you want to use Lerna commands, you need to run them as mentioned in BUILD.md: |
I'm going to close the issue since it's not a bug. It's just that sometimes it's tricky to setup Node, npm, etc. correctly. |
Wow, you didn't even wait for me to respond! Anyway, here are the currently globally installed packages on my Mac:
And here is the relevant portion of
(Note: it's pretty much exactly the same as the above.) On my Linux computer:
Now I run the following:
Oh, look! All the same errors came back!
Hrm, I guess it's not actually fixed! Oh, and just to confirm that I'm actually on the current commit:
Your most recent commit, earlier today: EDIT: FYI I'm running Node 14.15.4 LTS, if that helps you reproduce the errors. |
I just completely uninstalled and then reinstalled
And, yes,
Again, the Python dependency is an upstream issue with
Note that the Let's what's next:
Hmmm! I wonder if globally installing |
I did some more digging in the build instructions, and there is, in fact, a section workarounds for macOS and Linux in EDIT: Oh, look, the |
Well, I've managed to fix both the Linux dependency issues and the macOS build issues. The Linux dependency issues seem to be just because I can't get the The macOS build error seems to have been due to the fact that I was using Node 15 rather than Node 14. All of the build errors went away when I manually downgraded. I can open an issue suggesting that the Node version be specified in |
For newer variations of the "npm removes depencies" bug, here's a search on the new https://github.com/npm/cli/issues?q=is%3Aissue+is%3Aopen+removes+dependencies The reason I linked the particular issue I did was that it had the most information and corroboration. Also incidentally people kept commenting that the bug was still present even well after the original author closed the issue. |
I have reams and reams of logs from
npm install
failing, but ultimately doing the following seemed to fix the problem:sudo apt install python
sudo npm install --global jetifier
sudo npm install --global gulp
sudo npm install --global rollup
The text was updated successfully, but these errors were encountered: