Bump ecmaVersion to 2022 at .eslintcr.json
mcm1957 opened this issue · 6 comments
I would suggest to change .eslintrc.json to define ecmaVersion 2022 instead of 2020.
See one "problem" with varaible definitions in js class reported as error by eslint 2020:
https://t.me/ioBroker_development/28349 and
https://t.me/ioBroker_development/28355
If change is accepted, I could of course try to make a PR.
At first look change should be done here:
create-adapter/src/lib/core/questions.ts
Line 1124 in 32d7657
On this side https://node.green/#ES2023 u can check supported features of nodejs/ecma 18.18.2 is ecma 2023.
To increase trust - is a link from here: https://nodejs.org/en/docs/es6/
Ok
When removing node 16 from creator 2023 could be used ....
Didn't you write in Telegram that you were removing Nodejs 16 from the Creator?
Yes I did - comment should be a confirm to update to 2023 ... :-)
I thought about this again. As this setting is merely used to get ESLint to parse new syntax, we might also set it to esnext
and forget about it entirely.
is this the same as latest
?