This should get a list of problems maybe

This could be better adddressed when the Plugin Hook Loader API Exists and would get used without Package.json resolve or at last a none magical package.json resolve that is explicitly written in a reuseable loader.. As that exists in all other Engines also

Also interristing observation

all none nodejs ECMAScript engines that depend on ECMAScript do not have any module reuse exchange problems.
all none nodejs ECMAScript engine ship NodeJS or a NodeJS fork to load ECMAScript Modules written for NodeJS as a language.
- It is importent to keep in mind ECMAScript is a UTF8 Char based language it should run without nativ code anywhere.
- console.log('') should not require a 4gb stack of binary instructions. to build in a away that it is useable in many places out of the box.

Identified Fundamentals when incremental upgrading CJS to ESM

noSideEffects everything with a sideEffect is not a Module its a Script.
try to run the code isolated with "use strict" on top if it works it is a indicator that you can do a ESM Wrapper where you use import and correct the namedExports and then bundle that to get relativ clean ESM if the CJS code has no additional dependencies left over so is already like a bundle.
make sure that there is no usag of this. outside Classes. functions that use this are highly danger later for code hardening and security analyzes Many people like the author of "clean code" a book that maybe all know here pointed that out. This security reasons are by the way a blocker for commercial adoption of ECMAScript in general.
- see: above mentioned educational fundamental problems. As rule of thumb you need to be execution Context aware.
You should treat JS/ECMAScript like lua with dynamic JIT Build abilitys. in Fact a lua and ECMAScript have many common and the amount of ECMAScript engines is exploding so it gets more and more a lua replacement.
You should be aware of the fact that there will be no original Python 4 and the reasons for that.

Short Conclusion

package.json when used for anything else then referencing a main + dependencies is a bad thing. For Example the new import maps features overlap with ECMAScript import as soon as used you need to recode them the reuse the code. This could be directly done as additional js file that only injects the dependencie specifiers.

also the whole scripts section can be replaced by simply putting the same scripts into the folder and run node script.js and not npm run-script build which calles node build.js the list is endless. Then on Top the Require CJS breaks everything as it simply supports to much diffrent resolutions and module types.

Solution ways

the most easy compat fix for at last the require CJS problem would be to let require return module and not module.exports this way it would algin with the ECMAScript spec so it exports a object with string specifiers "exports":

Create doc on how to support ESM and CommonJS when publishing modules #542

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions