Skip to content

feat(no-unsupported): Support node 23.0.0 and 22.10.0#358

Merged
scagood merged 1 commit intomasterfrom
add-support-for-node-22_10-23_0
Oct 18, 2024
Merged

feat(no-unsupported): Support node 23.0.0 and 22.10.0#358
scagood merged 1 commit intomasterfrom
add-support-for-node-22_10-23_0

Conversation

@MichaelDeBoey
Copy link
Copy Markdown
Member

Closes #356
Closes #357

@MichaelDeBoey MichaelDeBoey added enhancement rule:update An update to a current rule labels Oct 17, 2024
@MichaelDeBoey MichaelDeBoey requested review from a team and scagood October 17, 2024 19:26
@MichaelDeBoey MichaelDeBoey self-assigned this Oct 17, 2024
Comment thread lib/unsupported-features/node-builtins-modules/module.js Outdated
Comment thread lib/unsupported-features/node-builtins-modules/worker_threads.js Outdated
// module.events
CustomEvent: events.CustomEvent,
CloseEvent: { [READ]: { supported: ["23.0.0"] } },
CustomEvent: {[READ]: { experimental: ["18.7.0", "16.17.0"], supported: ["23.0.0"] } },
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🤯 I mostly look at the global docs page, that could be annoying...

I wonder if we should ask someone from Node themselves?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Indeed annoying, but that's what the docs are saying. 🤷‍♂️

I think we should always stick to what the docs are saying.

I do think it would be a good idea to have a discussion with people on the Node team to find out if docs are incorrect and if so, update the docs (and our code).

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I see thanks for the explanation here 🙇: #358 (comment)

@MichaelDeBoey MichaelDeBoey force-pushed the add-support-for-node-22_10-23_0 branch from e2d546c to 9b5f2ec Compare October 17, 2024 19:42
Comment thread lib/unsupported-features/node-builtins-modules/process.js
@aladdin-add aladdin-add mentioned this pull request Oct 18, 2024
Comment thread lib/unsupported-features/node-globals.js
@MichaelDeBoey MichaelDeBoey force-pushed the add-support-for-node-22_10-23_0 branch from 9b5f2ec to 50f95c2 Compare October 18, 2024 14:29
Copy link
Copy Markdown

@scagood scagood left a comment

Choose a reason for hiding this comment

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

Thank you 💜

@scagood scagood changed the title feat: support Node 22.10.0 & 23.0.0 feat(no-unsupported): Support node 23.0.0 and 22.10.0 Oct 18, 2024
@scagood scagood merged commit 0fd0350 into master Oct 18, 2024
@scagood scagood deleted the add-support-for-node-22_10-23_0 branch October 18, 2024 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

✨ Node v23.0.0 support ✨ Node v22.10.0 support

3 participants