chore: replace resolver-oxc with new resolver-typescript

[JounQin]

Hi, eslint-plugin-import-x and eslint-import-resolver-typescript owner here.

The brand new eslint-import-resolver-typescript is now powered by unrs-resolver which is fork of oxc-resolver and rspack-resolver with P'n'P support and more targets, and it has competitive performance compared with eslint-import-resolver-oxc.

Before with resolver-oxc:

 socket-cli on  main [$!] ❯ TIMING=1 npmR check:lint

> [email protected] check:lint
> eslint --report-unused-disable-directives .

Rule                                | Time (ms) | Relative
:-----------------------------------|----------:|--------:
import-x/namespace                  |  1131.479 |    62.1%
@typescript-eslint/return-await     |   288.136 |    15.8%
import-x/order                      |    98.431 |     5.4%
import-x/extensions                 |    30.366 |     1.7%
n/no-extraneous-import              |    19.631 |     1.1%
n/no-unsupported-features/es-syntax |    18.692 |     1.0%
n/no-extraneous-require             |    17.510 |     1.0%
import-x/no-duplicates              |     9.148 |     0.5%
no-misleading-character-class       |     8.638 |     0.5%
import-x/default                    |     8.380 |     0.5%
is 📦 v0.14.67 via  v23.7.0 took 15s

After with resolver-typescript:

 socket-cli on  main [+] ❯ TIMING=1 npmR check:lint

> [email protected] check:lint
> eslint --report-unused-disable-directives .

Rule                                | Time (ms) | Relative
:-----------------------------------|----------:|--------:
import-x/namespace                  |  1058.428 |    65.0%
@typescript-eslint/return-await     |   225.935 |    13.9%
import-x/order                      |    71.322 |     4.4%
import-x/extensions                 |    27.978 |     1.7%
n/no-extraneous-require             |    15.662 |     1.0%
n/no-extraneous-import              |    15.299 |     0.9%
n/no-unpublished-import             |    12.542 |     0.8%
n/no-unsupported-features/es-syntax |    11.428 |     0.7%
n/no-unpublished-require            |     9.040 |     0.6%
no-misleading-character-class       |     8.839 |     0.5%
is 📦 v0.14.67 via  v23.7.0 took 10s

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, eval, network, shell	+28	51.9 MB

🚮 Removed packages: npm/[email protected]

View full report↗︎

[socket-security-staging]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell	+28	11.6 MB	jounqin

🚮 Removed packages: npm/[email protected]

View full report↗︎

[socket-security-staging]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Unpopular package	npm/[email protected]	Location: Package overview	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What are unpopular packages?

This package is not very popular.

Unpopular packages may have less maintenance and contain other problems.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[JounQin]

Actually, rules like n/no-extraneous-require/n/no-extraneous-import can just be remove in favor of no-extraneous-dependencies alreay covering them.

[jdalton]

Thank you @JounQin. Holding for more thorough review.

[JounQin]

@jdalton By the way, I have troubles when running npm run bs locally

 socket-cli on  chore/import_resolver ❯ npmR bs

> [email protected] bs
> npm run build:dist; npm exec socket --


> [email protected] build:dist
> del-cli 'dist' && rollup -c .config/rollup.dist.config.mjs


/Users/JounQin/Workspaces/GitHub/socket-cli/src/cli.ts, /Users/JounQin/Workspaces/GitHub/socket-cli/src/constants.ts, /Users/JounQin/Workspaces/GitHub/socket-cli/src/shadow/npm/bin.ts, /Users/JounQin/Workspaces/GitHub/socket-cli/src/shadow/npm/inject.ts → dist/module-sync...
created dist/module-sync in 5.3s

/Users/JounQin/Workspaces/GitHub/socket-cli/src/cli.ts, /Users/JounQin/Workspaces/GitHub/socket-cli/src/constants.ts, /Users/JounQin/Workspaces/GitHub/socket-cli/src/shadow/npm/bin.ts, /Users/JounQin/Workspaces/GitHub/socket-cli/src/shadow/npm/inject.ts → dist/require...
created dist/require in 4.9s
node:internal/modules/cjs/loader:1397
  throw err;
  ^

{
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/JounQin/Workspaces/GitHub/socket-cli/node_modules/@pnpm/lockfile-file/lib/logger.js',
    '/Users/JounQin/Workspaces/GitHub/socket-cli/node_modules/@pnpm/lockfile-file/lib/write.js',
    '/Users/JounQin/Workspaces/GitHub/socket-cli/node_modules/@pnpm/lockfile-file/lib/index.js',
    '/Users/JounQin/Workspaces/GitHub/socket-cli/dist/module-sync/cli.js'
  ]
}

Node.js v23.7.0

---

OK, should be related to Node v23 only because it tries require(ESM) automatically.

[jdalton]

Updated independently. Thank you @JounQin!