eslint-import-resolver-typescript

eslint-import-resolver-typescript copied to clipboard

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/import-js/eslint-import-resolver-typescript). This repository currently has no open or...

renovate[bot]

feat: better cache support via hashobject for example

4

JounQin

https://github.com/lukeed/resolve.exports

JounQin

tsconfig.json "references" is not evaluated

7

When reading tsconfig.json, it seems to be ignoring the "references" array which includes paths to other tsconfig files in the same directory. You can reproduce my repo with `npm init...

DrJume

Typescript NodeNext path alias with extension

7

I have a typescript project with `moduleResolution: 'NodeNext'`. In my `tsconfig.json`, I have set up an alias which points directly to a file. In the ES spec, this would be...

WoodyWoodsta

fix: resolve modules if folder contains a package.json file

2

getMappedPath resolves files by trying a number of different file extensions and filtering out those that aren't a file. This does not work when a TSConfig path alias resolves to...

sanderson-ut

"Unable to resolve path to module" in monorepo, after Angular 13 upgrade

5

After upgrading to Angular 13, which only supports Angular Package Format and ESModules, we are seeing "Unable to resolve path to module" issues. Our code is a monorepo using Yarn...

sanderson-ut

Related https://github.com/import-js/eslint-plugin-import/pull/2519#issuecomment-1230993695 and https://github.com/privatenumber/get-tsconfig/issues/38

JounQin

Performance degradation since version 3.1.0

2

Hi, I'm seeing a clear performance degradation ever since I upgraded from v2.7.1 -> v3.X At first I thought it was related to eslint-plugin-import but after trying the [eslint-plugin-i](https://github.com/un-es/eslint-plugin-i) version...

eyaldar

Inherit `project` configuration from `@typescript-eslint/parser`'s `parserOptions`

8

Using [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/parser#parseroptionsproject) is recommended to set `project` in `parserOptions`. We also need to add the `project` in `import/resolver-> typescript` when using _eslint-import-resolver-typescript_. Can we omit the first `project` or do...

carlocorradini