| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Not sure if this is due to flaky CI or not... will try again once other CI jobs are looking greener. |
Sorry, something went wrong.
|
Turns out there was an issue with symlinks on Windows in fixtures, which should be resolved now. Latest CI: https://ci.nodejs.org/job/node-test-pull-request/13773/ |
Sorry, something went wrong.
|
for the commit name, should the subsystem be esmodule or loader or something? module makes me think it touches the cjs module stuff |
Sorry, something went wrong.
|
CI error this time seems to be completely unrelated, so I believe this is good to merge. |
Sorry, something went wrong.
|
@devsnek esmodules isn't formally a subsystem I don't believe, although perhaps it should be? That said modules makes sense to me for both too. |
Sorry, something went wrong.
|
Rebased, latest CI: https://ci.nodejs.org/job/node-test-pull-request/13962/ Will actually merge this time. |
Sorry, something went wrong.
PR-URL: #19388 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #19388 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
The CommonJS module resolver specifically skips --preserveSymlinks for the main entry point into Node.
From discussion in #19383, it seems like this should probably be carried over into the ES module resolver in order to ensure full backwards-compatibility.
The alternative here might be to have --preserveSymlinks act on the main in the CJS resolver too instead of this PR.
//cc @nodejs/modules
Checklist