there is a conflict now.

there is a conflict now.

Resolved now.

@mdjermanovic does this change mean that espree 10 (and thus, eslint 9) can't ever support ecmaVersion 2025, which includes import assertions?

espree 10 and eslint 9 already fully support ecmaVersion 2025.

Thanks; I clarified that in the discord. It turns out it's a different issue with eslint; i'll keep looking into it.

Hi, I have a dependency in my project @typescript-eslint-parser that uses "eslint-visitor-keys": "^5.0.0", and since this commit was released, my yarn install command is falling with the error:

error eslint-visitor-keys@5.0.1: The engine "node" is incompatible with this module. Expected version "^20.19.0 || ^22.13.0 || >=24". Got "22.9.0"

My project is using Node 22.9 and it won't be an easy task to upgraded because of many CI/CD pipelines and submodules configured. So, I have some questions:

• Since this is a change that can break many projects, the version released here shouldn't be 6.x.x?
• What's the problem with Node lower than 22.13 that forced this changes?

Thanks

Hi, I have a dependency in my project @typescript-eslint-parser that uses "eslint-visitor-keys": "^5.0.0", and since this commit was released, my yarn install command is falling with the error:

error eslint-visitor-keys@5.0.1: The engine "node" is incompatible with this module. Expected version "^20.19.0 || ^22.13.0 || >=24". Got "22.9.0"

My project is using Node 22.9 and it won't be an easy task to upgraded because of many CI/CD pipelines and submodules configured. So, I have some questions:

• Since this is a change that can break many projects, the version released here shouldn't be 6.x.x?
• What's the problem with Node lower than 22.13 that forced this changes?

Thanks

Hi, I have a dependency in my project @typescript-eslint-parser that uses "eslint-visitor-keys": "^5.0.0", and since this commit was released, my yarn install command is falling with the error:

error eslint-visitor-keys@5.0.1: The engine "node" is incompatible with this module. Expected version "^20.19.0 || ^22.13.0 || >=24". Got "22.9.0"

My project is using Node 22.9 and it won't be an easy task to upgraded because of many CI/CD pipelines and submodules configured. So, I have some questions:

• Since this is a change that can break many projects, the version released here shouldn't be 6.x.x?
• What's the problem with Node lower than 22.13 that forced this changes?

Thanks

My bad, just saw that the it was released as Breaking Change from 4.2.1 to 5.0.0.