Build Tools: Remove deprecated esModuleInterop: false from tsconfig - #77009
Build Tools: Remove deprecated esModuleInterop: false from tsconfig#77009manzoorwanijk wants to merge 1 commit into
esModuleInterop: false from tsconfig#77009Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
The `esModuleInterop=false` option is deprecated in TypeScript 6.0 and will stop functioning in TypeScript 7.0. Removing it now keeps the same default behavior while eliminating the deprecation warning. `allowSyntheticDefaultImports: true` already handles default imports for type-checking.
85070bc to
03f3a94
Compare
|
Flaky tests detected in 03f3a94. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23913399924
|
|
Closing in favor of #77010 |
1 participant
What?
Remove the deprecated
esModuleInterop: falsesetting fromtsconfig.base.json.Why?
The
esModuleInterop=falseoption is deprecated in TypeScript 6.0 and will stop functioning in TypeScript 7.0, producing a warning in the IDE. Removing it now eliminates the warning while keeping the same default behavior (false).allowSyntheticDefaultImports: truealready handles default imports for type-checking.How?
Removed the
esModuleInterop: falseline and its associated comment fromtsconfig.base.json.Testing Instructions
npm run build— should complete successfully.tsconfig.jsonin an IDE — the deprecation warning should be gone.Testing Instructions for Keyboard
N/A — no UI changes.
Use of AI Tools
This PR was authored with the assistance of Claude Code (claude-opus-4-6).