Can't package with nodejs 12.13.0
See original GitHub issueBrief Issue Summary
Node moved their LTS to 12.13.0 recently and I can’t get vsce package
to run for
vscode-cmake-tools anymore
Expected:
- run
yarn
- run
npm install -g vsce
- run
vsce package
- get a visx package
Apparent Behavior:
yarn
– runs OKnpm install -g vsce
– runs OKvsce package
Executing prepublish script 'npm run vscode:prepublish'...
ERROR Command failed: npm run vscode:prepublish
warning cmake-tools@1.2.0: The engine "vscode" appears to be invalid.
Assertion failed: len < MAX_ENV_VAR_LENGTH, file c:\ws\deps\uv\src\win\util.c, line 1476
error Command failed with exit code 3221226505.
npm ERR! code ELIFECYCLE
npm ERR! errno 3221226505
npm ERR! cmake-tools@1.2.0 vscode:prepublish: `yarn run compile-production`
npm ERR! Exit status 3221226505
npm ERR!
npm ERR! Failed at the cmake-tools@1.2.0 vscode:prepublish script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\chbarto\AppData\Roaming\npm-cache\_logs\2019-11-01T23_17_44_312Z-debug.log
It looks like this error is in libuv someplace. Looking at libuv src/win/util.c
I see MAX_ENV_VAR_LENGTH is 32767. My largest env var is ~2000 bytes (It’s PATH).
Platform and Versions
- Operating System: Microsoft Windows 10 Enterprise (x64) Build 19013.1
- CMake Tools Extension Version: master
- nodejs version: v12.13.0
- vsce version: 1.69.0
- yarn version: 1.19.1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (4 by maintainers)
Top Results From Across the Web
npm does not support Node.js v12.18.3 - Stack Overflow
I've installed the latest version of Node.js (12.18.3) on my Windows 10 PC and I'm trying to install a package using npm.
Read more >Node v12.13.0 (LTS)
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Read more >Prevent npm install for not supported Node.js versions
Use a local npm configuration to prevent users from installing your module/project with an unsupported Node.js version.
Read more >Node JS 12.13.0 - Chocolatey Software
Version Downloads Last Updated Status
Node JS 19.3.0 5292 Wednesday, December 14, 2022 Waiting for Maintainer
Node JS 19.2.0 25193 Wednesday, November 30, 2022 Approved
Node...
Read more >Manage Node.js versions using asdf - LogRocket Blog
Before installing the Node plugin, we first have to install GnuPG to verify the authenticity of the package. There are different requirements ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Actually, it’s a yarn issue: https://github.com/yarnpkg/yarn/issues/7783
Another way to work around it is to delete the contents of NOTICE.txt.
This appears to be fixed with latest tools. Node 12.18.4 works.