replace npm with pnpm #2
Closed
Conversation
This file contains 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
Contributor
perryd01
commented
Dec 19, 2024
•
perryd01
commented
- swaps npm lock to pnpm
- updates all packages
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hmm. At this scale im not sure, if we need to use pnpm. Its probably easier for the others, if we stick to npm for now. But the version updates are welcome for sure. |
|
well, its easy to install it on any OS, also used by Next. js (since it works great with monorepos) and often outperforms npm on clean installs. |
|
updated packages with npm in #4 |
perryd01
force-pushed
the
package-update
branch
from
b11065e to
00088cc
Compare
perryd01
force-pushed
the
package-update
branch
from
00088cc to
8a4858b
Compare
|
wont do |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.