[Bug]: LavaPack is not defined

[aminbakhshi]

Describe the bug

I am not sure if this is a bug or what, but I cannot run metamask locally, I have this warning error message that "LavaPack is not defined" , I have set up and then run the develop branch, BUT, when I switch to lavamoat-dev-optional, I can run the metamask locally without any problem, but the problem is that this branch is not updated and I don't have many new features.

Could someone help me out here to see what's the problem, and why these set of error messages appears on the console.

Steps to reproduce

Error messages or log output

No response

Version

develop branch

Build type

No response

Browser

Chrome

Operating system

Windows

Hardware wallet

No response

Additional context

No response

[aminbakhshi]

@danjm Could you please help me with this if you can

[dfibuch]

This isn't exactly a fix but there is a workaround that I found. I'm running WSL with Ubuntu 18.04 and I cloned the repo there, followed the setup steps again and that problem is no longer there, it all works.

[brad-decker]

This is most likely due to not running yarn setup, but can also be a mismatch between operating system specifics with lavamoat.

1. Run yarn setup
2. Run yarn start and check if the extension runs locally for you
3. If step 2 fails, run rm -rf node_modules/
4. yarn setup
5. yarn lavamoat:auto

If my conjecture is correct, the last step will result in your build policies being updated. If you are working on putting together a PR, do not include these changes with your commits because they will be incompatible with our CI environment 🤪 -- this is something we are hoping to correct soon. Please follow up if you have rectified your situation :)

[HowardBraham]

Duplicate of #13318