fix: deprecate default export in favor of named export #641
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.
This deprecates the default export in favor of the new named export
sveltePreprocess
. It's done to ensure a better interop between CJS and ESM without resorting to hacks in the future. It also enables people using"module": "NodeNext"
in theirtsconfig.json
to import without type errors. The sub exports were also adjusted so that the transpiled TS output doesn't include__importDefault
wrappers, which makes Node's static analysis miss those named exports.Related: #591 (comment)
Before submitting the PR, please make sure you do the following
pnpm lint
!)Tests
npm test
orpnpm test