MetaMask / metamask-extension Build error on Windows10

[AsadullahSoomro]

Currently, I am trying to build Metamask on windows 10 using Nodejs v14.17.6

yarn run v1.22.11
$ lavamoat development/build/index.js
(Error#1)

Error#1: LavaMoat - required package not in whitelist: package "@gulp-sourcemaps\map-sources" requested "through2" as "through2"
at requireRelative (LavaMoat/core/kernel:414:15)
at requireRelativeWithContext (LavaMoat/core/kernel:366:16)
at Object.eval (\work\metamask-extension\node_modules@gulp-sourcemaps\map-sources\index.js:4:15)
at internalRequire (LavaMoat/core/kernel:353:25)
at requireRelative (LavaMoat/core/kernel:394:27)
at requireRelativeWithContext (LavaMoat/core/kernel:366:16)
at Object.eval (\work\metamask-extension\node_modules\gulp-sourcemaps\index.js:7:15)
at internalRequire (LavaMoat/core/kernel:353:25)
at requireRelative (LavaMoat/core/kernel:394:27)
at requireRelativeWithContext (LavaMoat/core/kernel:366:16)

OS: Windows 10
MetaMask Version: 10.1.0
Node v14.17.6
Yarn v1.22.11
error screenshot here:

[ryanml]

@AsadullahSoomro - did you run yarn setup or just yarn?

[AsadullahSoomro]

@AsadullahSoomro - did you run yarn setup or just yarn?
@ryanml
yes, sir,it is running but right now another exception coming when I am just trying to clone the metamask using

MetaMask/metamask-extension from github

I am just following the docs, but ended up in error when access the extension via browser
Uncaught ReferenceError: LavaPack is not defined
context
background.html

I have tried to get it resolve but unable to find any clue

[jonathansampson]

Adding my name to the list of people experiencing these issues.

The yarn dist command fails entirely for me (I ran yarn setup prior):

The yarn start command succeeds, but I too see a slew of Uncaught ReferenceError: LavaPack is not defined errors on the background page.

A bit of bisecting reveals f196c9f to be the first bad commit (with regards to building on Windows). I suppose it's not surprising :)

The issue could be with the escaping of back-slashes in package names:

Note here how @babel/core is not escaped when requested as a package:

But it is escaped when its own packages are requested:

[Gudahtt]

Thanks for the report! This is a duplicate of #10748. Please follow that issue for updates.