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
When will 4.0 be released on npmjs.com? #1665
Comments
@nodejs/node-gyp Thoughts? I'd be okay with releasing v4.0, we have enough interesting changes to merit a release. |
No objections. There was a vague plan last summer (#1519) but I think enough has landed to warrant a release. |
#1670 should land before v4.x is released. Any other obsoletisms that ought to be scrapped? |
Can we please get this done? Is there a problem merging #1670 and then releasing 4.0? |
This issue (and other problems with the Javascript/Node ecosystem) convinced us that using Electron/Node/Javascript for serious applications is a non-starter and we abandoned our project in favor of a native implementation that is done in 10% of the time and with total control and zero dependencies. The binary size for the rewritten tool is 2.2 MB, and that is statically linked and with all necessary assets (icons etc.) embedded. Electron is a huge mistake. Trying to use a browser for everything is simply ineffective and uses too many resources. |
Right now we can't build any native modules that work with Electron 4, because they require the delayed windows hook, which is enabled only with node-gyp 4.0. We don't want to fork and modify each and every dependency so we can enable it locally. Is there a good reason not to release node-gyp 4?
The text was updated successfully, but these errors were encountered: