resolvePackageRoot logic is incorrect

[NullVoxPopuli]

This will traverse back to the root of the disk -- and we want to stop at a git-boundary.

I guess, if there is a git boundary -- not every project will use git

[lifeart]

It's expected behaviour, because packageRoot is not equal to projectRoot, npm may lookup till user homedir for global node_modules.

It’s because we have to work in virtual env, like browsers, we can’t rely on project root dir, for monorepo case package may be under project (on top-level node-modules)

[NullVoxPopuli]

I think, development wise, i way need to work in tmp then! Lol

[lifeart]

@NullVoxPopuli it's better to always be in web-container, because there no trust for js ecosystem!

[NullVoxPopuli]

how do you do that locally? in stackblitz-based things, perf seems kinda slow 😅

[lifeart]

@NullVoxPopuli no web containers on my side, just crossing my fingers once doing npm install! 😂