Before You File a Proposal Please Confirm You Have Done The Following...

• I have searched for related issues and found none that match my proposal.
• I have searched the current rule list and found no rules that match my proposal.
• I have read the FAQ and my problem is not listed.

Relevant Package

parser / typescript-estree

My proposal is suitable for this project

• I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Description

From @bradzacher's #8424 (comment):

Oh @JoshuaKGoldberg we can fix that! https://github.com/import-js/eslint-plugin-import/blob/7a21f7e10f18c04473faadca94928af6b8e28009/utils%2Fparse.js#L80-L85

I'd forgotten that I'd added this to their setup. We just need to add more deletes. Perhaps we should add a util function to our project so we can control this without touching their code??

Let's do it! Or, actually: eslint-plugin-import does not have a production dependency on any of our packages. And it features a long tail of backwards compatibility for Node.js versions that we don't support. My suspicion (cc @ljharb) is that even if we create & export this utility, eslint-plugin-import might not be able to use it directly.

Filing an issue over there... import-js/eslint-plugin-import#2962 -> https://github.com/import-js/eslint-plugin-import/pull/2963/files#r1485342911

Additional Info

No response