| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com> Co-authored-by: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
|
It looks like make test-doc is failing. |
Sorry, something went wrong.
| ".": "./main.js", | ||
| "./submodule": "./src/submodule.js" | ||
| ".": "./index.js", | ||
| "./submodule.js": "./src/submodule.js" |
There was a problem hiding this comment.
| "./submodule.js": "./src/submodule.js" | |
| "./submodule": "./src/submodule.js" |
Sorry, something went wrong.
There was a problem hiding this comment.
i still think these examples shouldn't be changed to add the extension.
Sorry, something went wrong.
There was a problem hiding this comment.
I don’t really understand what’s motivating this change either, if anything that adds more bloat to the import maps – I mean it adds 3 bytes; jokes aside, it could give the reader the impression that using an extension is required when defining an export path, and/or confuse needlessly the package consumers on why the is no submodule.js file at the trot of the package – whereas extensionless makes a good job signaling we’re not dealing with actual paths imo.
(Same thing for the change main.js -> index.js, I don’t think it’s necessary)
That being said, I don’t feel strongly about this, so feel free to disregard.
Sorry, something went wrong.
|
|
||
| ```js | ||
| import submodule from 'es-module-package/submodule'; | ||
| import submodule from 'es-module-package/submodule.js'; |
There was a problem hiding this comment.
| import submodule from 'es-module-package/submodule.js'; | |
| import submodule from 'es-module-package/submodule'; |
Sorry, something went wrong.
Co-authored-by: Jordan Harband <ljharb@gmail.com>
|
The docs should only reflect node's present, not node's (quite uncertain) future wrt import maps. When node supports import maps, and the feature is sadly unable to support the most common node ecosystem pattern, then that would be the appropriate time to have opinionated docs - not now, when it's still just wishful thinking from a few collaborators. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the iteration here; I think this does a great job minimizing editorializing in the node docs. LGTM.
Sorry, something went wrong.
| ".": "./main.js", | ||
| "./submodule": "./src/submodule.js" | ||
| ".": "./index.js", | ||
| "./submodule.js": "./src/submodule.js" |
There was a problem hiding this comment.
i still think these examples shouldn't be changed to add the extension.
Sorry, something went wrong.
|
Added some final clarifications to the extensions guidance and hoping to land this soon. |
Sorry, something went wrong.
| ".": "./main.js", | ||
| "./submodule": "./src/submodule.js" | ||
| ".": "./index.js", | ||
| "./submodule.js": "./src/submodule.js" |
There was a problem hiding this comment.
I don’t really understand what’s motivating this change either, if anything that adds more bloat to the import maps – I mean it adds 3 bytes; jokes aside, it could give the reader the impression that using an extension is required when defining an export path, and/or confuse needlessly the package consumers on why the is no submodule.js file at the trot of the package – whereas extensionless makes a good job signaling we’re not dealing with actual paths imo.
(Same thing for the change main.js -> index.js, I don’t think it’s necessary)
That being said, I don’t feel strongly about this, so feel free to disregard.
Sorry, something went wrong.
PR-URL: #43375 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: #43375 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
|
This needs a backport PR to land on v16.x-staging. There is a conflict because of the "Subpath folder mappings" section and I'm not sure where to put it. |
Sorry, something went wrong.
|
Thanks, I've posted a backport in #43809. |
Sorry, something went wrong.
PR-URL: nodejs/node#43375 Backport-PR-URL: nodejs/node#43809 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
| Back | FazBrowse Home | New Git URL |
This updates the packages documentation to update some of the modules "exports" guidance with the Node.js 12 EOL, specifically:
/cc @nodejs/modules