fix(vite-plugin): change default export to named export #1465
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I don't see a way to fix that other than change default export to named.
if i make vite-plugin package true ESM, it requires other packages also being ESM (lingui/conf + lingue/cli/api)
and that's not possible for many different reasons
Usually, when you use transpires, they insert an "interop" for all default imports. That interop actually checking if there a "default" property.
Native nodejs ESM loader obviously doesn't have it. So commonjs modules transpiled from ESM source is not supported by node in aspects of default exports.
it's a common issue in other packages as well. So to normally work with native ESM you either should be fully ESM itself, or not use default export as a workaround.
Now package exports both, default and named exports. I also updated documentation to use named export.
Types of changes
Fixes #1449
Checklist