Validate choice of `PathToExport` name in ES Modules
Closed this issue · 0 comments
andreaphylum commented
In this bit, the ESM PathToExport
is named default
only if a condition is satisfied (the default export scope should be the same scope of the last accessed node).
Is this expected behavior? This form of export would, regardless, expose a symbol of default
to be imported by dependents. Is the name
field used only for display purposes, and thus it would make more sense to represent this as an identifier rather than default
?
We should investigate this and build unit tests to validate our intentions.