-
Notifications
You must be signed in to change notification settings - Fork 18
support for pnpm and pnpx #8
Comments
This project is not maintained by the nx team so the package currently don't have support for pnpm. I'll use this issue to track the development of this feature. Unfortunately I'm the only maintainer and during this period I've no time to dedicate to this project. If someone wants to give me a hand on this it will be very much appreciated. |
@JacopoPatroclo thanks for reply. I'll just be patient. (I'm far from having the skills to overtake this project, but I'll try to have a look). |
For anyone who is interested, I wanted to share some findings/context from my investigation. ContextIf you find yourself in this repo, it's probably fairly evident that getting RN / Expo projects to work within a monorepo is uniquely challenging. Generally, this stems from module resolution API disparity between node packagers and the metro bundler. (But also, shoutout to unexpected caching issues -- the next most encumbering issue with RN/Expo dev) Packaging with pnpmThe module resolution issues are particularly challenging when using Possible course of actionThis repo includes a I would love to work on this but pnpm support isn't an immediate priority for my project -- but I hope this helpful in advancing the topic. And big ole thanks to Jacopo for this repo -- made some very cool things possible in my world 🙏 |
I'm getting the same error when using yarn nx start
|
I'm wondering whether this (excellent) plugin supports also
pnpm
I have created a nx workspace with
pnpm, pnpx
as packages manager following this announcement stating nx supports pnpm.But after I've started metro bundler, with
pnpx nx start <app-name>
I get this error:Even if I use
npx nx start <app-name>
Thanks for the great work!
The text was updated successfully, but these errors were encountered: