Migrate to pnpm #1457
Closed
Migrate to pnpm #1457
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wesenbergg
reviewed
Jan 14, 2025
|
Thanks for the interest! For now, I prefer to keep the template simple with plain npm. I think it's totally fine for people and teams to adopt pnpm if preferred, but for this template I'll keep it as it is for now. Given that, I'll close this one, but thanks for the effort! ☕ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I simply migrated from npm to pnpm to benefit from increased performance. I had to add zod to package.json because of the way npm and pnpm deal with dependencies. It also made sense to add it as an explicit dependency, as it is being imported in two files in the frontend/src/routes/_layout folder (admin.tsx & items.tsx).
Cheers!