MetaMask / MetaMask/metamask-extension
Ensure test build is the same as prod build
Open
Nobody has claimed this yet.
area-buildSystem
contributor experience
type-enhancement
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
We recently merged a PR whose tests passed, but whose prod build failed. We could avoid this with consistent builds between those environments!
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 files, tests, or entry points are named. Start by locating the test and production build configurations, then compare the commands and environment inputs they use. Done means the two environments use a consistent build process and the previously reported mismatch is covered by a reproducible verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100