Is it possible to avoid public hoisting (nohoist behaviour from yarn workspaces) with node-linker=hoisted?

[rrebase]

In React Native Monorepo setups setting node-linker=hoisted is a must to have module resolution play well with metro. However, seems that there's no way in pnpm to avoid public hoisting (deps being installed in root node_modules instead of project) similar to what yarn workspaces nohoist would do, is that true? Anyway to disable it?

The following does not have any effect with node-linker=hoisted

public-hoist-pattern[]='!@types/react'
hoist-pattern[]='!*eslint-plugin*'

[rrebase]

@zkochan do you have any thoughts/input here? 🙏

[rrebase]

@zkochan Sorry to 🏓 again, but have you had the chance to investigate this?

[zkochan]

public-hoist-pattern will not work with node-linker=hoisted

For hoisting limit here is a PR: #6468

[merojosa]

@rrebase, did you use a workaround for this situation?

[rrebase]

@merojosa yep, used temporary workarounds depending on the dep that blew up. In one case locked same package to different patch versions so that it wouldn't be hoisted 🙈

Haven't tried myself yet. But with the latest metro version supporting unstable_enableSymlinks might be able to drop node-linker=hoisted altogether

[0xPT]

@rrebase this worked for me! I have a React Native/Expo app and another app that I need to nohoist in the same monorepo. The new metro feature allowed me to remove node-linker=hoisted.

[spigelli]

https://pnpm.io/npmrc#hoist-pattern

[rrebase]

Unfortunately this does not work as described if using node-linker=hoisted

[hydra1983]

I have to set shared-workspace-lockfile=false in .npmrc to fix this problem