Use explicit TypeScript import extensions - #9637
Open
dibarbet wants to merge 2 commits into
Open
Conversation
Upgrade TypeScript and task execution so relative TypeScript imports can use explicit source extensions while preserving CommonJS output. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c12a1e5a-fd95-478e-b642-d8911d7d81e1
Avoid the tsx require hook conflict when Jest loads TypeScript configuration through ts-node. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c12a1e5a-fd95-478e-b642-d8911d7d81e1
This was referenced Aug 5, 2026
JoeRobich
approved these changes
Aug 5, 2026
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
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.
Summary
Preparatory extraction from #9635 that adds explicit
.tsextensions to relative TypeScript import, export, and dynamic-import specifiers without adopting ESM.rewriteRelativeImportExtensionsmodule: "CommonJS",moduleResolution: "node",package.jsonmain, and the existing CommonJS esbuild/Jest configurationtsx; retains updatedts-nodeonly for Jest-driving task scripts because Jest 29 loads TypeScript configs throughts-node.jsJest requests back to TypeScript sourceValidation
npm run compileDevnpm run test:unitnpm run omnisharptest:unitnpm run packageDev(producesdist/extension.jswith CommonJS exports)