import-js / import-js/eslint-import-resolver-typescript
Support for reading bundler's config
- Dominant language
- TypeScript
- Stars
- 825
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
All major bundlers have a `resolve` configuration, for example:
- https://vite.dev/config/shared-options.html#resolve-alias
- https://webpack.js.org/configuration/resolve/#resolve
- https://rspack.dev/config/resolve
We can read users' config file and get the normalized `resolve` config to align ESLint's module resolution with the bundler’s behavior.
[Some features implemented in `eslint-import-resolver-oxc`](https://github.com/9romise/eslint-import-resolver-oxc/issues/40):
- auto-detect bundler configs
- export a function to transform the config
If anyone has more ideas, please feel free to discuss, and I'd be happy to port this feature to this repository.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the linked Vite, webpack, and Rspack resolve documentation, then examine the referenced eslint-import-resolver-oxc issue for its config auto-detection and transformation approach. Define the supported bundler configurations and how their normalized resolve settings should align ESLint module resolution; done means the agreed behavior is implemented and covered by project tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100