-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Actually set impliedNodeFormat in more cases #59479
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
Conversation
@typescript-bot test it |
Hey @andrewbranch, the results of running the DT tests are ready. Everything looks the same! |
@andrewbranch Here are the results of running the user tests with tsc comparing Everything looks good! |
@andrewbranch Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@andrewbranch Here are the results of running the top 400 repos with tsc comparing Something interesting changed - please have a look. Details
|
It's a shame this missed the beta... but I guess we should fix this oops now since we said we were going to do it? |
const moduleResolution = getEmitModuleResolutionKind(options); | ||
const shouldLookupFromPackageJson = ModuleResolutionKind.Node16 <= moduleResolution && moduleResolution <= ModuleResolutionKind.NodeNext | ||
|| pathContainsNodeModules(fileName); | ||
return fileExtensionIsOneOf(fileName, [Extension.Dmts, Extension.Mts, Extension.Mjs]) ? ModuleKind.ESNext : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not for this PR but we copy and paste the arrays passed into fileExtensionIsOneOf
all over the place; makes me wonder if we'd get a speed boost by lifting these arrays into common variables.
A bad merge conflict resolution in #58825 caused it not to take effect. This finishes the job.