5 Replies
Hi @qdeehwee. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, there's currently no official support for using pnpm instead of npm in Wasp projects. Wasp is specifically designed to work with npm as its package manager.
The documentation and GitHub issues indicate that:
1. Wasp projects use a standard
package.json file for dependencies, which is located at the root of your project Dependencies documentation.
2. There's a GitHub issue (#853) where a user asked about using custom npm registries, but there's no mention of alternative package managers like pnpm GitHub Issue #853.
3. In a Discord support thread, a community member specifically asked about choosing a different package manager (mentioning pnpm and bun), indicating this isn't currently supported.
4. Wasp has specific requirements for Node.js (version >= 18) and uses npm for package management Quick Start documentation.
If you need to use pnpm for your project, you might want to consider creating a feature request on the Wasp GitHub repository, as there doesn't appear to be an existing issue specifically addressing support for alternative package managers like pnpm.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @qdeehwee, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Hey @qdeehwee, sadly still no support for other package managers like bun or pnpm.
Thanks, is it on roadmap?
Yes, but not on the shorter one. In the long run we want to support them, but that will most likely come after 1.0.
Alright thank you