Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fix types under node16 moduleResolution #441

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

me4502
Copy link
Contributor

@me4502 me4502 commented Aug 4, 2023

The types of this library do not match the actual JS code, leading to a situation where using ESM under the node16 moduleResolution method in TypeScript, the default export types will fail to resolve. TypeScript is more strict around type compliance with these settings enabled, and therefore requires the types to match.

The JS code does not use a default import, as export default in ESM is not identical to module.exports = . export = can be used in the index.d.ts to match the behaviour within the JS file.

More information on this specific issue is available here, https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/FalseExportDefault.md

The types of this library do not match the actual JS code, leading to a situation where using ESM under the `node16` moduleResolution method in TypeScript, the default export types will fail to resolve. TypeScript is more strict around type compliance with these settings enabled, and therefore requires the types to match.

The JS code does not use a default import, as `export default` in ESM is not identical to `module.exports = `. `export =` can be used in the `index.d.ts` to match the behaviour within the JS file.

More information on this specific issue is available here, https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/FalseExportDefault.md
@jaywcjlove jaywcjlove merged commit 2767829 into jaywcjlove:master Dec 8, 2023
github-actions bot pushed a commit that referenced this pull request Dec 8, 2023
The types of this library do not match the actual JS code, leading to a situation where using ESM under the `node16` moduleResolution method in TypeScript, the default export types will fail to resolve. TypeScript is more strict around type compliance with these settings enabled, and therefore requires the types to match.

The JS code does not use a default import, as `export default` in ESM is not identical to `module.exports = `. `export =` can be used in the `index.d.ts` to match the behaviour within the JS file.

More information on this specific issue is available here, https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/FalseExportDefault.md 2767829
jaywcjlove added a commit that referenced this pull request Dec 8, 2023
github-actions bot pushed a commit that referenced this pull request Dec 8, 2023
jaywcjlove added a commit that referenced this pull request Dec 9, 2023
github-actions bot pushed a commit that referenced this pull request Dec 9, 2023
@me4502 me4502 deleted the master-1 branch December 11, 2023 02:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants