Improved tsconfig: Target the actual feature set of Node >=12 #173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
es6
also goes by the name ofes2015
and eg. async/await didn't arrive untiles2017
while Node 12 actually supports evenes2019
fully.Rather than keeping track of all of that in here, and ensuring to stay up to date here when new LTS versions gets released, I included a shared recommended minimal tsconfig as a base tsconfig for eg. that data.
On top of that I also added
declarationMap
to get source maps which maps from.d.ts
to the original.ts
files. This helps in debugging things and looking things up in eg. VSCode.Sorry for not updating the lock file, my local yarn was acting up (I've moved to npm again myself since a few months so my new computer haven't really had yarn on it)
Also sorry for not using proper styling of the commit messages, maybe you can do a squash merge and/or cherry pick and set the correct commit messages then?