Skip to content

Use Node 22 (current LTS) for development#573

Merged
adamkudrna merged 1 commit into
masterfrom
maintenance/node-22
Nov 4, 2024
Merged

Use Node 22 (current LTS) for development#573
adamkudrna merged 1 commit into
masterfrom
maintenance/node-22

Conversation

@adamkudrna

@adamkudrna adamkudrna commented Oct 21, 2024

Copy link
Copy Markdown
Member
  • Drop Node 18 for testing builds.
  • Add Node 22.x to dev engines.

@bedrich-schindler

Copy link
Copy Markdown
Contributor

I would update package.json in such way, that I would remove engines section and introduce devEngines:

  "devEngines": {
    "node": "20.x || 22.x"
  },

This is how React does it. RUI does not required any specific version to run, only dev environment does.

What do you think @adamkudrna @mbohal ?

@mbohal

mbohal commented Oct 22, 2024

Copy link
Copy Markdown
Contributor

I agree with using devEngines. However the code example provided by @bedrich-schindler is wrong.

See: https://docs.npmjs.com/cli/v10/configuring-npm/package-json#devengines for usage. I wonder if we should fail or warn on error. I think I would prefer to fail…

@mbohal
mbohal self-requested a review October 22, 2024 11:57
@bedrich-schindler

Copy link
Copy Markdown
Contributor

@mbohal good point. It is weird that library like React have it wrong, but you are right unless there is some undocumented approach.

Comment thread package.json
Comment thread .github/workflows/lint.yml
Drop Node 18 for testing builds. Add Node 22.x to dev engines.
@adamkudrna adamkudrna changed the title Use Node 22 (upcoming LTS) for development Use Node 22 (current LTS) for development Nov 4, 2024
@adamkudrna
adamkudrna merged commit 3808ce4 into master Nov 4, 2024
@adamkudrna
adamkudrna deleted the maintenance/node-22 branch November 4, 2024 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants