Add flag to preserve dynamic import #727
Merged
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.
Progress toward #726
This PR adds a new
preserveDynamicImport
flag that, when enabled, changes theimports
transform so that only staticimport
s are transformed, while dynamicimport()
expressions are passed through as-is.This behavior matches what TypeScript does when handling a
.cjs
file whenmodule: nodenext
is specified, and ts-node expects transpilers to handle thismode, so this PR is a necessary step toward Sucrase as a ts-node plugin.
This mode also seems like the best interpretation of
import()
in new codethese days; if
import()
is transpiled, then it's impossible to access ESMcode from CJS in Node, so leaving it alone allows a mechanism to import
ESM-only libraries. My tentative plan is to change this mode to be the default
behavior in an upcoming semver-major release.