Uh oh!
There was an error while loading. Please reload this page.
Link to WinterCG Runtime Keys in export conditions docs - #48408
Conversation
nodejs-github-bot
commented
Jun 10, 2023
Review requested:
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
guybedford
left a comment
There was a problem hiding this comment.
Thanks for working this through
Uh oh!
There was an error while loading. Please reload this page.
anonrig
left a comment
There was a problem hiding this comment.
I feel like we should wait for the proposal to be finalized before merging this.
guybedford
commented
Jun 10, 2023
@Ethan-Arrowood would be great to have your review on this one. |
Uh oh!
There was an error while loading. Please reload this page.
Ethan-Arrowood
left a comment
There was a problem hiding this comment.
LGTM - fwiw WinterCG is a W3C Community Group. We can't actually "publish" specifications/standards yet beyond "draft". I think runtime keys is in a stable enough place to be referenced here.
anonrig
commented
Jun 10, 2023
Thanks @Ethan-Arrowood. We are using the word |
Ethan-Arrowood
commented
Jun 10, 2023
Proposal and draft are synonymous I believe. I'm not a stickler about it |
anonrig
commented
Jun 11, 2023
@jcbhmr can you fix the linter issues? |
jcbhmr
commented
Jun 11, 2023
It was that one of the lines was a bit too long. 😆 I think I've fixed it! 👍 |
anonrig
commented
Jun 11, 2023
@jcbhmr Can you squash all commits and make sure that the first commit explains what this pull request does? If we add |
Done! 😊 Now there's a single commit: [link-to-runtime-keys a3a2cc26cd5] doc: remove non-Node.js export conditions & link to WinterCG Runtime Keys
Author: Jacob Hummer <jcbhmr@outlook.com>
1 file changed, 9 insertions(+), 4 deletions(-)I did this: git reset --soft origin/main
git commit -m ...as described here: https://stackoverflow.com/questions/25356810/git-how-to-squash-all-commits-on-branch |
anonrig
commented
Jun 12, 2023
Thanks. The commit message is too long. Please take a look at commit message guidelines. |
This commit: 1. Adds a link to the WinterCG Runtime Keys proposal draft spec in the documentation for the `export` condition. 2. Adds a criteria to add more export conditions to the Node.js docs: they should be Node.js core-relevant. 3. Removes the "deno" and "react-native" export conditions from the core docs with the expectation that readers will follow the link to the Runtime Keys proposal draft spec to learn about them and more.
I've rewritten the commit message. ❤️ |
nodejs-github-bot
commented
Jun 20, 2023
Landed in 43c3d9f |
This commit: 1. Adds a link to the WinterCG Runtime Keys proposal draft spec in the documentation for the `export` condition. 2. Adds a criteria to add more export conditions to the Node.js docs: they should be Node.js core-relevant. 3. Removes the "deno" and "react-native" export conditions from the core docs with the expectation that readers will follow the link to the Runtime Keys proposal draft spec to learn about them and more. PR-URL: #48408 Reviewed-By: Guy Bedford <guybedford@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit: 1. Adds a link to the WinterCG Runtime Keys proposal draft spec in the documentation for the `export` condition. 2. Adds a criteria to add more export conditions to the Node.js docs: they should be Node.js core-relevant. 3. Removes the "deno" and "react-native" export conditions from the core docs with the expectation that readers will follow the link to the Runtime Keys proposal draft spec to learn about them and more. PR-URL: nodejs#48408 Reviewed-By: Guy Bedford <guybedford@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit: 1. Adds a link to the WinterCG Runtime Keys proposal draft spec in the documentation for the `export` condition. 2. Adds a criteria to add more export conditions to the Node.js docs: they should be Node.js core-relevant. 3. Removes the "deno" and "react-native" export conditions from the core docs with the expectation that readers will follow the link to the Runtime Keys proposal draft spec to learn about them and more. PR-URL: nodejs#48408 Reviewed-By: Guy Bedford <guybedford@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit: 1. Adds a link to the WinterCG Runtime Keys proposal draft spec in the documentation for the `export` condition. 2. Adds a criteria to add more export conditions to the Node.js docs: they should be Node.js core-relevant. 3. Removes the "deno" and "react-native" export conditions from the core docs with the expectation that readers will follow the link to the Runtime Keys proposal draft spec to learn about them and more. PR-URL: #48408 Reviewed-By: Guy Bedford <guybedford@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit: 1. Adds a link to the WinterCG Runtime Keys proposal draft spec in the documentation for the `export` condition. 2. Adds a criteria to add more export conditions to the Node.js docs: they should be Node.js core-relevant. 3. Removes the "deno" and "react-native" export conditions from the core docs with the expectation that readers will follow the link to the Runtime Keys proposal draft spec to learn about them and more. PR-URL: #48408 Reviewed-By: Guy Bedford <guybedford@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
This PR would...
cc @guybedford
follow up of #48407