v1.7.0 requires node v8
See original GitHub issueHi we noticed that newly created projects started breaking on our CI that is still using node v6 with following error:
/[redacted]/node_modules/source-map-explorer/index.js:463
...result,
^^^
SyntaxError: Unexpected token ...
It is referring this code: https://github.com/danvk/source-map-explorer/blob/dad76525f0d0928aab205eb4d9b0c16d875bad92/index.js#L462-L465
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Previous Releases - Node.js
Version Date V8 npm NODE_MODULE_VERSION
Node.js 19.3.0 2022‑12‑14 10.8.168.21 9.2.0 111 Downloads C...
Node.js 19.2.0 2022‑11‑29 10.8.168.20 8.19.3 111 Downloads C...
Node.js 19.1.0 2022‑11‑14 10.7.193.20 8.19.3...
Read more >Upgrading Node.js to latest version - Stack Overflow
If you just need to upgrade your old version of Node.js to the latest one and don't need multiple versions, simply over-write your...
Read more >Download & Update Node.js to the Latest Version! Node v19 ...
Direct download links to update to the latest Node.js versions: Node v19.0.0 / LTS v16.18.0.
Read more >npm does not support Node.js v10.15.2 · Issue #1877 - GitHub
It looks like current installed npm is not compatible with Node.js version you are using. You'll probably need to update your npm using...
Read more >Switching between Node versions during development
We compare and contrast two popular Node version managers that can help you more easily switch between Node versions during development.
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
You can continue using
v1.6.0
. Sorry, but I don’t think we should stick with node 6 support@jakub300 Your point about semver is well-taken and we’ll keep it in mind in the future. If you’d be interested in getting SME working with Node 6 I’d be happy to merge a PR and cut a 1.7.1 release. But otherwise, given that node 6 is so close to EOL, I’d prefer to leave things as-is.