js-dxtools / js-dxtools/webpack-validator
Strict mode - If `noParse` is defined, check that it doesn't overlap with loader definitions
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 290
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Given noParse is stronger than loader definitions, it is easy to end up in a situation where you have a loader definition that gets rejected. This can be a little hard to spot so it would be nice to at least warn agains the situation is detected.
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
The issue names no files or tests. Start by locating strict-mode validation for noParse and loader definitions, then determine how overlapping definitions are detected and reported. Done means an overlap produces a warning without changing the existing rejection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100