Open kotletmotlet opened 7 months ago
I’ve ran into similar issue recently. You should be able to break the cycle by reminding browserlist peerDep from update-browserslist-db via yarn’s patch protocol. If update-browserslist-db is not a direct dep of your project you might also have to used resolutions to force the patched version to be used
note that when using patch you’ll have to manually edit the path to the patch in package.json to use relative path instead of ~
I've tried migrating my react project with workspaces to yarnpnp2nix, but encountered error during package building with nix build `
I suspect that it has something to do with how the yarn-manifest.nix is generated, because of code that looks like a cyclic dependency ( packages."browserslist@npm:4.22.3 referring to update-browserslist-db@npm:1.0.13 and update-browserslist-db@npm:1.0.13 back to former)
Does anyone have idea how to fix it?