7 ms·
I'm currently working in a pnpm monorepo and it really seems like a potential double edged sword. On the one hand I have longed for better support for local pac
by worldsayshi 2y ago
I'm currently working in a pnpm monorepo and it really seems like a potential double edged sword. On the one hand I have longed for better support for local packages in the ecosystem (which pnpm does provide, and I'm happy for it). But some weird edge cases seem to arise. Like serverless functions not being supported[1]. I suppose that's just a matter of feature maturity.
The more design-level hazard of this might be that it's easier to build monorepos where everything is tightly coupled. And you end up with something that is like a single package with extra abstraction layers.
1 - https://github.com/pnpm/pnpm/issues/6259 https://github.com/pnpm/pnpm/issues/6259
- forty 2y agoIsn't the problem with serverless only a problem with windows not supporting zipped symlinks ? (From what I understand from the GH ticket)
- deleted 2y ago[deleted]
- ricardobeat 2y agoIsn’t that what `pmpm deploy` solves? It should copy all packages into the target dir.
- deleted 2y ago[deleted]
- worldsayshi 2y agoIt tries to solve it but doesn't seem to get all the way there. Symlinks are still very much present for example. But I'm still a bit confused what exactly is causing the azure function to fail so I can't say more.