-
Notifications
You must be signed in to change notification settings - Fork 46
Docs/review of various affects of type field #475
Comments
Thanks for collecting that list!
That sounds like a bug or at least unexpected behavior. The loader for the entry point should be determined by the file format of the entry point, not by the closest
Yep, sounds inconsistent to me. It should complain on all "explicitly ESM or otherwise incompatible files", regardless of the |
It is if a .cjs or .mjs is seen, but the algorithm is actually a bit more complex to reason about than just that, see shouldUseESMLoader's impl |
For
Just as |
removing the modules-agenda label for now. Please feel free to re-add |
"type"
inpackage.json
has a few affects:.js
within that package boundary (not extension-less files?)We should probably document and/or bugfix these if they are not the expected behavior.
The text was updated successfully, but these errors were encountered: