Remove remaining esModuleInterop usage#77095
Conversation
Remove `esModuleInterop` from `bin/tsconfig.json` and `packages/wp-build/tsconfig.json`, and remove the now-unnecessary re-export comment in `packages/core-data/src/hooks/memoize.js`.
|
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. |
|
Size Change: -9 B (0%) Total Size: 7.74 MB 📦 View Changed
ℹ️ View Unchanged
|
|
Flaky tests detected in 47eab5f. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/24083766696
|
Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org> Co-authored-by: jsnajdr <jsnajdr@git.wordpress.org>
What?
Follow up to #77010 (comment)
Removes the remaining
esModuleInteropcompiler option from the codebase.Why?
As pointed out in the linked review comment,
esModuleInteropwas still enabled inbin/tsconfig.jsonandpackages/wp-build/tsconfig.json. This option is unnecessary and its removal was missed in #77010.How?
esModuleInterop: truefrombin/tsconfig.jsonesModuleInterop: truefrompackages/wp-build/tsconfig.jsonpackages/core-data/src/hooks/memoize.jsTesting Instructions
npx tsc --project bin/tsconfig.json --noEmitandnpx tsc --project packages/wp-build/tsconfig.json --noEmitnpm run buildand verify no errors.Use of AI Tools
Claude Code was used to create the commit and PR.