-
Notifications
You must be signed in to change notification settings - Fork 1.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
All npm run <command>
fails on GitLens v9.4.1 source code on macOS Mojave
#644
Comments
@billsedison What is the output from the commands? |
@eamodio There is not specific output,
This is only observed on macOS, no such issue on Ubuntu 18.04 and Windows 10. |
@billsedison Could this be related: https://stackoverflow.com/questions/53602337/node-and-npm-too-slow-to-start-after-install-of-macos-mojave If you wait a while does it actually start? |
From the output -- it looks like its trying to run the command. I'm at a loss. I would recommend reaching out to npm and ask them or dig into npm's trace logs. |
Nope, it never actually starts even I wait for 1 minute.
The problem is the If I reduce the size of package.json, for example, by removing Is it possible to move some configurations outside of |
Again, I would still recommend reaching out / filling an issue with npm. npm deals with this fine on other OS' (and later versions of macOS I believe) and package-lock.json files are much larger. As for breaking it up -- I would think it is possible with some sort of build step to put the files back together, but given what would be built would be |
Okay, noted. Thanks. |
Sorry I don't have anything better to offer -- I'm at a loss. 😢 |
No problem at all, thank you. At least I have some tricky workaround to bypass it by reducing the package.json size for now, it's been enough for my local development. 😄 |
👍 Can also just use webpack directly -- the npm scripts themselves aren't really tricky at all. |
Yes, exactly! |
Going to close this since there isn't much I can do here given the |
can you use nps? https://www.npmjs.com/package/nps edit package.json: "scripts": { Then create a package.scripts.js file for the build targets? |
I've just switched to |
@billsedison @kburson Could you try and see if the latest yarn nightly resolves the issue for you? |
Yarn 1.19 is out which contains a fix for this issue. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to Reproduce:
You'll see no
dist
folder is generated. If you use VSCode to open it, and run F5, the extension is not runnable.All
npm run <command>
fails.The issue is the size of the package.json file. It is around 220KB.
On removing some fields to reduce the file size,
npm run
commands work fine.The text was updated successfully, but these errors were encountered: