modules
modules copied to clipboard
nodejs
Node.js Modules Team
It seems we have some research to do about how WASI expects to run as entry points vs modules. This is just a tracking issue for now to figure out...
I have not been closely following the conversation here (maybe that was a mistake for me), but it means I missed the transition out of experimental (not a cli flag...
Internally in the fork, we seem to have an `extensionFormatMap`, which is ~something~ [exactly](https://github.com/nodejs/ecmascript-modules/blob/da0667d4b0c4fcd26b595a5af3fafd6d743cd2d1/lib/internal/modules/esm/default_resolve.js#L18-L23) like: ```js { '__proto__': null, ".js": "cjs" '.cjs': 'cjs', '.js': 'esm', // obviously this shouldn't be...
Right now ESM uses `code: 'ERR_MODULE_NOT_FOUND'` while CJS throws a similar error with `code: 'MODULE_NOT_FOUND'`. So far that looks to be accidental and worth fixing so code that catches these...
I work with appoptics-apm and have been watching progress on ECMAScript modules from a distance for a while. I'd like to thank everyone for wrestling with the complexities involved in...
Hello, module team. May I get help with the way to load packages without cache? I have seen a bit of odd behavior in `import(cjs)`. --- > Copied from https://github.com/nodejs/node/issues/29812...
Currently we can access the default `resolver` when in a `--loader` loader. However we can't access this loader from a regular program. I'd like to propose exposing this function as...
Just tracking tooling encountering issues with what we have been rolling out, please add more as they are seen for gathering overall impact: issue | resolved | summary ---- |...
In the ["How do loaders declare what hooks they implement?"](https://docs.google.com/document/d/1J0zDFkwxojLXc36t2gcv1gZ-QnoTXSzK1O6mNAMlync/edit#heading=h.kwm3bfcwaypt) part of the loaders design document, it makes several claims regarding loaders imported by third parties: > Loaders can expose...
Just a heads up I bumped `lodash-es` to use `type` of `module` and got reports of breakage due to various `npm` versions. See https://github.com/lodash/lodash/issues/4359.
