Use @next/canary due to a memory leak #203
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
oscard0m
force-pushed
the
revert-202-revert-201-upgrade-eslint-rules-with-next-recommended
branch
from
a526cef to
6240f2a
Compare
oscard0m
changed the title
This reverts commit d41e635.
oscard0m
force-pushed
the
revert-202-revert-201-upgrade-eslint-rules-with-next-recommended
branch
from
6240f2a to
42b263d
Compare
oscard0m
deleted the
revert-202-revert-201-upgrade-eslint-rules-with-next-recommended
branch
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.
Reverts #202
Uses @next/canary due to a memory leak: vercel/next.js#36703