import-js / import-js/eslint-plugin-import
Webpack resolver does not work when webpack exports a promise configuration
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
As of webpack v2, the webpack configuration file can export a Promise: https://webpack.js.org/configuration/configuration-types/#exporting-a-promise.
The webpack resolver does not attempt to resolve that promise to use the configuration.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named in the issue. Start by tracing how the webpack resolver loads configuration, using the linked webpack configuration-types documentation as context. Done means the resolver handles configurations exported as Promises without losing the webpack settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript, webpack
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100