How to configure metro bundler to run eslint on transpile code and update?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 696
- Avg merge
- 8m
- Merged PRs (30d)
- 7
Description
Metro bundler has something like eslint-webpack-plugin solution, like middleware or something? Something that will prevent to compile my code until I fix all eslint or typescript errors and warnings?
I'm looking tirelessly for a way, but I can't find anyone with the same problem. Not allowing to compile the code because of errors in the eslint or in the typescript should be something that the metro should do, to bring more security to the code.
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 repository files, tests, or entry points are named. Start by examining Metro's configuration and bundling flow, then compare the requested behavior with the eslint-webpack-plugin approach. Done means documenting or implementing a supported way to block compilation when ESLint or TypeScript errors and warnings remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript, react-native, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100