Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark (synchronous) import.meta.resolve(…) as implemented in node v20.6.0 #20726

Merged
merged 3 commits into from
Sep 18, 2023

Conversation

lgarron
Copy link
Contributor

@lgarron lgarron commented Sep 17, 2023

Release notes documenting that this is now available without a flag: https://nodejs.org/en/blog/release/v20.6.0

Note that the experimental version became synchronous in v20.0.0 (still behind a flag at the time): https://nodejs.org/en/blog/release/v20.0.0

…v20.6.0

Release notes documenting that this is now available without a flag: https://nodejs.org/en/blog/release/v20.6.0

Note that the experimental version became synchronous in v20.0.0 (still behind a flag at the time): https://nodejs.org/en/blog/release/v20.0.0
@github-actions github-actions bot added the data:js 📟 Compat data for JS/ECMAScript features. https://developer.mozilla.org/docs/Web/JavaScript label Sep 17, 2023
@github-actions github-actions bot added the data:browsers 🌍 Data about browsers (versions, release dates, etc). This data is used for validation. label Sep 17, 2023
@@ -68,15 +68,7 @@
"version_added": false
},
"nodejs": {
Copy link
Member

Choose a reason for hiding this comment

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

Use an array; don't remove old versions' information.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sounds good. I wasn't sure how to handle 20.0.0 — should I include all three versions?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done!

Copy link
Member

@Elchi3 Elchi3 left a comment

Choose a reason for hiding this comment

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

Thanks! 👍

@Elchi3 Elchi3 merged commit 63526f8 into mdn:main Sep 18, 2023
4 checks passed
@lgarron lgarron deleted the node-20.6-import.meta.resolve branch September 18, 2023 20:23
Elchi3 pushed a commit to Elchi3/browser-compat-data that referenced this pull request Nov 14, 2023
…v20.6.0 (mdn#20726)

* Mark (synchronous) `import.meta.resolve(…)` as implemented in `node` v20.6.0

Release notes documenting that this is now available without a flag: https://nodejs.org/en/blog/release/v20.6.0

Note that the experimental version became synchronous in v20.0.0 (still behind a flag at the time): https://nodejs.org/en/blog/release/v20.0.0

* [nodejs.json] Add `node v20.6.0`.

* Include the full `node` compat history for `import.meta.resolve(…)`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:browsers 🌍 Data about browsers (versions, release dates, etc). This data is used for validation. data:js 📟 Compat data for JS/ECMAScript features. https://developer.mozilla.org/docs/Web/JavaScript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants