Testing: Switch default ESLint resolver to improve handling for modern exports semantics#72893
Testing: Switch default ESLint resolver to improve handling for modern exports semantics#72893
Conversation
|
Size Change: 0 B Total Size: 2.38 MB ℹ️ View Unchanged
|
manzoorwanijk
left a comment
There was a problem hiding this comment.
I thought we already had this kind of setup.
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @RichForever. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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. |
What?
Closes #72136
Closes #68395
Updates the ESLint configuration to specify
eslint-import-resolver-typescriptas the resolver foreslint-plugin-import.Why?
See rationale in #72136
Testing Instructions
Verify lint passes:
npm run lint:js