fix: use separate .d.ts types for import vs .d.cts for require - #6275
Open
deepshekhardas wants to merge 1 commit into
Open
fix: use separate .d.ts types for import vs .d.cts for require#6275deepshekhardas wants to merge 1 commit into
deepshekhardas wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #5686.
Problem
The
exportsfield inpackage.jsonusestypes: "./index.d.cts"for bothimportandrequireconditions. When TypeScript's module resolution is set tonodenext, the.d.ctsextension signals CJS module format, causing TypeScript to apply CJS interop rules — producingz.z.*paths in emitted declarations and breaking type inference in ESM projects.Fix
Split the
typescondition per import/require:import→types: "./index.d.ts"require→types: "./index.d.cts"Applied to all export subpaths (mini, locales, v3, v4, etc.).