feat(node-resolve): Resolve js/jsx/mjs/cjs imports from TypeScript files #1498
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.
Rollup Plugin Name:
node-resolve
This PR contains:
Are tests included?
Breaking Changes?
If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers: #1465
Description
This patch is a combination of PRs #1475 and #1454. It updates the logic for importing from within a TypeScript file. In that case,
.js
can now resolve to.ts
and.tsx
,.jsx
can resolve to.tsx
,.mjs
can resolve to.mts
, and.cjs
can resolve to.cts
. This behavior was verified to mimic that oftsc
itself. Importing from within plain JS files is untouched (e.g., a.js
import from within a.js
file will not resolve to.ts
).