MetaMask / MetaMask/metamask-extension
[Bug]: Loading extension fails with `LavaMoat - required package not in whitelist`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Describe the bug
Unable to use local build extension.
- Chrome 98.0.4758.102
- Ubuntu 20.04.
- Node 14.17.6
- Yarn 1.22.17
Steps to reproduce
- Follow instructions on README for local build or alternatively yarn start.
- Follow instructions to add the build to Chrome.
Edit: same happens in Firefox
Error messages or log output
Uncaught LavaMoat - required package not in whitelist: package "browserify-sha3" requested "js-sha3" as "js-sha3"
Version
10.10.2
Build type
No response
Browser
Chrome
Operating system
Linux
Hardware wallet
No response
Additional context
I have noticed users already reported this type of build problems in the past, but no clear solution was given afaik. Please feel free to close this issue in favor of an existing one where there is a follow-up on this topic.
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 with the local-build instructions in README and docs/add-to-chrome.md, then reproduce with yarn start and inspect the reported LavaMoat whitelist error for browserify-sha3 requesting js-sha3. Done means a locally built extension can be loaded in Chrome or Firefox without this error; the issue names no source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100