import-js / import-js/eslint-plugin-import
Aliases in imports
Open
`exports` support
question
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
If I have node v16.13.1 and eslint 8.4.1, should eslint ([without](https://github.com/johvin/eslint-import-resolver-alias#usage) `"settings"` in eslintrc file) use node resolving for aliases configured with package.json?
package.json:
```
...
"imports": {
"#common/*": "./src/common/*.js"
},
...
```
Contributor guide
Research direction
Start by examining how the plugin reads package.json and the eslintrc settings when resolving imports. Reproduce the Node v16.13.1 and ESLint 8.4.1 configuration with the shown imports mapping, then determine whether the expected alias should resolve and add or update coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100