Projen defaults to a deprecated node version (10.17.0)
See original GitHub issueThis leads to mysterious build failures like
node_modules/@sinonjs/fake-timers/types/fake-timers-src.d.ts:11:28 - error TS2304: Cannot find name 'queueMicrotask'.
11 queueMicrotask: typeof queueMicrotask;
It would be best to default to an LTS version of NodeJs types (14 at the moment).
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
projen/projen: A new generation of project generators - GitHub
By default, the new command will also execute this program, which will result in a fully working project. Once your project is created,...
Read more >API Reference | projen
AwsCdkDepsJs, Manages dependencies on the AWS CDK for Node.js projects. ... Default: false; releaseWorkflow ( boolean ) DEPRECATED: renamed to release .
Read more >NPM warn message about deprecated package - Stack Overflow
This command will analyze installed NPM-packages and their versions. The report will contain: package name; latest version; current version; dependency path ( ...
Read more >Node.js platform history - AWS Elastic Beanstalk
This page lists the current and previous versions of AWS Elastic Beanstalk's Node.js platform branches and the dates that each version was current....
Read more >Deprecated APIs | Node.js v19.3.0 Documentation
A Runtime deprecation will, by default, generate a process warning that will be ... The legacy HTTP parser, used by default in versions...
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 Free
Top 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
I don’t think there’s any specific needs to support older NodeJs version - I think we’re just trying to minimize the number of downstream repos we need to make manual changes to (but at some level it might be unavoidable).
Also note to self - when we are are upgrading the default Node version, we can also change the default tsconfig.json “lib” value from es2018 to es2019, since all of es2019 is supported by Node 12 and above according to https://node.green/.
Closing this issue as it hasn’t seen activity for a while. Please add a comment @mentioning a maintainer to reopen.