fix: regenerated pnpm-lock.yaml #35
Merged
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
Closed
|
Deploy preview for irvinehacks-site-2024-sanity ready!
|
|
Deploy preview for irvinehacks-site-2024 ready!
|
|
Think the issue is there's a regular npm |
samderanova
force-pushed
the
fix/incompatible-pnpm-lock
branch
from
84aece1
to
fd45405
Compare
taesungh
approved these changes
Nov 24, 2023
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.
This is an attempt to resolve #34 , in which Vercel throws a warning saying that the
pnpm-lock.yamlfile is "incompatible", by deleting and regenerating it.