Skip to content

update the node version to latest LTS - #1229

Merged
sabrine33 merged 5 commits into
develfrom
update-node-version
Jul 31, 2026
Merged

update the node version to latest LTS#1229
sabrine33 merged 5 commits into
develfrom
update-node-version

Conversation

@sabrine33

@sabrine33 sabrine33 commented Jul 29, 2026

Copy link
Copy Markdown
Contributor
  • update the node version to latest LTS 24.18.0

  • update tsconfig file accordingly to : https://github.com/tsconfig/bases/

  • reverting the tsconfig.file file as that requires ts upgrade along other libraries too. And setting the target to 'esnext' as that latest ECMAScript version.
    The "target" option in tsconfig.json tells the TypeScript compiler which version of JavaScript to compile your code down to.

@sabrine33
sabrine33 requested review from khelwood and yoldas July 30, 2026 09:41
Comment thread tsconfig.json Outdated
Comment thread tsconfig.json

@sabrine33 sabrine33 Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Module does not support es2024 (nor es2025) entry. - so left it to esnext

TypeScript hasn't defined a distinct module emit profile for those years because no new ECMAScript module-system features were introduced that would require one — es2022 already covers top-level await, and anything newer is folded into esnext.
esnext is a moving target that always maps to the latest module features TypeScript supports, so it's accepted even when a specific year isn't. If/when new module-level syntax lands (e.g. import attributes stabilizing), the team may add an es2024/es2025 value — but until then, only the explicitly listed years are valid.

setting target to es2024 - as failing with value not valid with es2025
lib does not support es2025 too
@sabrine33
sabrine33 merged commit 5af2bc5 into devel Jul 31, 2026
16 of 17 checks passed
@sabrine33
sabrine33 deleted the update-node-version branch July 31, 2026 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants