fix(vue-extractor): fix default export burden with /api/extractors/babel #1626
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
#1623 (comment)
If you have a ESM project and will try to use
vue-extractor
the import inside vue-extractor:Will fail. This is happened because
@lingui/vue-extractor
is a dual package code.In ESM context nodejs picking
.mjs
file (followingimport
condition in package.json) which tries to import@lingui/cli/api/extractors/babel
which is cjs downleveld from ESM and the way how typescript compiles to cjs is not compatible with native ESM modules (additional .default appears)This all is a big non-solvable headache, which simply could be avoided by banning
export default