Merged
Conversation
🦋 Changeset detectedLatest commit: a4592fe The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
gdborton
previously approved these changes
Nov 7, 2023
Member
gdborton
left a comment
There was a problem hiding this comment.
LGTM, small nit to add PR description.
gdborton
reviewed
Nov 7, 2023
…' of github.com:vercel/vercel into zachward/onb-125-handle-too-many-projects-error-message
Ethan-Arrowood
approved these changes
Nov 8, 2023
Merged
Ethan-Arrowood
pushed a commit
that referenced
this pull request
Nov 8, 2023
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## vercel@32.5.3 ### Patch Changes - Handle `TooManyProjects` error in places where projects are created ([#10807](#10807)) - Updated dependencies \[[`89c1e0323`](89c1e03), [`fd29b966d`](fd29b96)]: - @vercel/node@3.0.9 - @vercel/next@4.0.14 ## @vercel/next@4.0.14 ### Patch Changes - Fixed headers for static routes when PPR is enabled ([#10808](#10808)) ## @vercel/node@3.0.9 ### Patch Changes - Replace usage of `fetch` with `undici.request` ([#10767](#10767)) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
This PR adds improved error handling for the 200 project limit error that will start being returned for free tier teams/accounts. The following changes have been made:
client.output.prettyErrorso that the docs link (https://vercel.com/docs/limits/overview#general-limits) returned with the error response is included with the error messagecreateProjectis called, which includes the following commands:vc project addvc link(indirectly called viaensureLink)vc list(indirectly called viaensureLink)vc git connect(indirectly called viaensureLink)Testing
@vercel.com), this is necessary for creating a team with the proper conditions to artificially trigger the error messagevtest314 too many projects, for examplevtest314 too many projects test 1vercel/vercel/packages/clipnpm dev add [project-name] --cwd=/path/to/some/projectScreenshot of error message when attempting to add project from cli
