Support for nohoist / multiple versions of the same package

[michelalbers]

What is the problem this feature would solve?

I have a monorepo with multiple frontends and multiple backend services. Some frontends are at the latest version of React and some are still using an older version. Same goes for the backends - some need older versions of express and some are using the most recent one.

With bun it seems that all dependencies are hoisted to the root and there can only be one version per package available. I would need to circumvent that problem with a nohoist option.

What is the feature you are proposing to solve the problem?

Introduce nohoist to give developers more control over specific hoisting needs.

What alternatives have you considered?

Using pnpm which stores the packages with a version tag so there are no clashes. But obviously I want to try bun :)

[frankcalise]

Also experiencing a need for this for a react-native project inside of a monorepo

[keverw]

I'm playing around with Ionic Framework and Capacitor. Looks like it complains if not in there directly even though they have multi-app support. For now my workaround is just to symlink it.

[coolcorexix]

desperately need this support too :( please let me know what I can help to speed up the development of this feature

[Scalahansolo]

To add to the list here, this is preventing Motion from using bun as our package manager in production.

[lkuoch]

@Jarred-Sumner any update for this?

[JRhodes95]

Likewise - our use-case is a design system that uses tailwind and asks consumers to scan the library's node_modules entry for class usage - similar to what Flowbite does.

Hoisting by default makes this marginally harder in monorepos as the relative path changes based on where it's hoisted to.

EDIT - it is also breaking font sourcing with vite where the font file is provided by the design system package and referenced in css.