Lars Kappert

Sounds like a plan! Is that something you would like to submit a PR for?

Hah, `alias` solves my issue completely, eg: ``` const empty = join(fileURLToPath(import.meta.url), '../empty.js'); const options = { interopDefault: true, extensions: DEFAULT_EXTENSIONS, esmResolve: false, alias: { '@rushstack/eslint-config/patch/modern-module-resolution': empty, '@rushstack/eslint-patch/modern-module-resolution': empty, },...

Let's just close this one, thanks @pi0! Keep up the great work.

Knip does not even read unused files, so it's currently unable to ignore it based on its contents, so that's why I'm going to close this issue for now. A...

Yeah that makes sense. Any chance you'd be up for a PR?

Thanks Paweł, useful to have that repro. Looks related to the issues you mention indeed. Hopefully easy to resolve in Knip, but need to dig some deeper. For starters, Knip...

It's different config but a "Go To Definition" still resolves it properly, so I was also thinking of looking into LSP stuff. Fwiw, it's quite literally sending `compilerOptions` from [ts.parseJsonConfigFileContent](https://github.com/webpro-nl/knip/blob/c80ac0e7f52440a0c5a5deb70e0d28070a3e1aa3/packages/knip/src/util/tsconfig-loader.ts#L9-L13)...

Knip has migrated from `enhanced-resolve` to [oxc-resolver](https://www.npmjs.com/package/oxc-resolver). This resolver sits in front of the TS internal module resolver. There seems to be no mention of `rootDirs` in docs nor the...

Thanks Adam, are you willing to open a pull request to improve this?

Thanks, @jmfrancois! Does this support paths like `key[0].into.deep[1]`? Would be great if there'd be test or two to confirm. Any chance you could add some?