js-dxtools / js-dxtools/webpack-build-analyzer
Provide info on how to fix `Module build failed: Unrecognised input
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This is the classic "loader doesn't match input" case. Webpack spews out Module build failed: Unrecognised input then.
Providing better information on how to fix this might go beyond the scope of webpack-validator, but I want to have the idea somewhere. The problem is that this is a check relying on Webpack output. If I remember right, stats might have this information on error. Perhaps a stats related tool would be the right place for this.
The issue comes up particularly with newbies so it would be cool to provide something little better here.
(from https://github.com/js-dxtools/webpack-validator/issues/84)
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
Start by reviewing how webpack-build-analyzer or webpack-validator consumes Webpack output for “Module build failed: Unrecognised input”, then inspect the referenced stats-related error information. Done means users receive clearer guidance for the loader/input mismatch, with the appropriate project boundary identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100