Replies: 1 comment 1 reply
-
Ah, this was a mere oversight by me when setting up typescript, I guess. I haven't made a conscious choice when specifying the node dependencies. You're right to assume that it should be lowered to 12.x to ensure types adhere to the reality. On the other hand the actual use of final JavaScript is pretty slim, so that it never imposed any real problems. You could look at the compiled JS, which might be a bit ugly, but it doesn't use anything fancy from more modern node versions. Also on the TypeScript side very little is used to make that dependency version difference noticeable. Unintentionally there is also the hope that AWS will add node 14 sooner than later to L@E, as node 10 is nearing it's EOL date (2021-04-30). This would leave us with a single maintained node version (12), which might be okay for most people, but newer versions not only come with features, but also bugfixes and performance improvements. Hey, AWS, if you're reading this, please add node 14 soon? Nevertheless I have lowered the @types/node to the 12 series to avoid any surprises. |
Beta Was this translation helpful? Give feedback.
-
I noticed that project uses NodeJS 14 types. However, I did not find any official release for L@E support of such. How are you able to support this?
Beta Was this translation helpful? Give feedback.
All reactions