Managing Prisma ORM in a @pnpmjs workspaces monorepo is simple!
Follow our step-by-step guide to:
📦 Generate Prisma Client properly to avoid type resolution issues
🔗 Share and reuse Prisma Client across apps
⚙️ Use the package in Next.js
pris.ly/guide/pnpm-workspace…
This whole time I've stuck with npm out of habit and because it "just works".
But then I had to override a subdependency via package.json, and npm just wouldn't do it. I spent hours fiddling.
So @darcy recommends I use @pnpmjs, and w/ the same package.json, it "just works".
pnpm is now featured on the @nodejs download page. How cool is that!
ALT A screenshot of the new Node.js download page from the node.js website, where from a dropdown you can select pnpm to get instructions about how to setup pnpm with Node.js
We’re planning to introduce “configurational dependencies” in pnpm.
These will be installed before all other dependencies, allowing repositories to share configurations.
Think patches, build allowlists, version catalogs, or even installation hooks.
RFC: github.com/pnpm/rfcs/pull/8
Looking back at the year, WebStorm is grateful to have supported projects like @PrettierCode, @pnpmjs, @tseslint, @geteslint, and @astrodotbuild.
Huge thanks to the open-source contributor volunteers whose hard work makes it all happen! 🎉✨
If you use pnpm libraries, you might have noticed that we released v900 and v1000 versions of libraries. This was done to avoid collisions while releasing from the v9 pnpm CLI branch and from v10. Also, the big version numbers allow us to have breaking changes in libraries.