silverwind

I'd definitely keep it at this point, it's too valuable and not everyone wants to install another dependency and fight its config just to replace one rule.

Why not: ```js { resolver: "webpack", resolverOptions: {/* resolver-specific options */}, }

> I don't like this idea of `resolver: 'webpack' | 'typescript'`. > > Let's do `resolver: require('@eslint-import/webpack')` and `resolver: import('@eslint-import/webpack')`. That would work and be preferred in flat config format....

I think the only modern resolution mechanisms one needs are these two (names based on [tsconfig `moduleResolution`](https://www.typescriptlang.org/tsconfig#moduleResolution)): - `node-16`: Node's resolution that requires file extensions. Likely should use [import.meta.resolve](https://nodejs.org/api/esm.html#importmetaresolvespecifier) and...

Is CJS support still desired? CJS packages could just remain on using `eslint-plugin-import`. Non-flat configs load as CJS but if I recall correctly, `import.meta.resolve` is also available there.

> > Non-flat configs load as CJS but if I recall correctly, `import.meta.resolve` is also available there. > > Flat config supports both CJS and ESM, so there is no...

Wild guess, but it seems that upgrading MacOS from 14.4.1 to 14.5 seems to have resolved this for me. Can anyone else confirm? Previously I reproduced this problem of failing...

Actually no, I'm again affected on latest MacOS. Will try to downgrade again, but from cursory tests before, downgrade did not help.

+1 on removal of `inspect` dependency and especially `eval` which also causes warnings during my build process in vite: ``` node_modules/@iarna/toml/lib/toml-parser.js (178:22): Use of eval in "node_modules/@iarna/toml/lib/toml-parser.js" is strongly discouraged...

Yes, different node major version have different ABI versions, so I would recommend including node major version in the cache key. Minor/patch versions should be strictly ABI compatible. Also see...