Repository navigation
chore: no rate limits under yarn dev - #357
Merged
Merged
Conversation
Testing a dev server by hand kept tripping them, with waits of over ten minutes. `yarn dev` now passes --dev, which turns them off. Setting GRYT_DISABLE_RATE_LIMITS=false keeps them on there, and NODE_ENV=production still ignores all of it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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
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.
Clicking around a dev server kept tripping the rate limits, with waits of over ten minutes.
GRYT_DISABLE_RATE_LIMITSalready existed, but you had to remember to set it.yarn devnow passes--dev, and that turns the limits off. I ran the server in each mode and checked the startup log:--watch ... --dev: limits off.node, as production runs it: limits on.GRYT_DISABLE_RATE_LIMITS=falsewith--dev: limits on.NODE_ENV=productionwith--dev: limits on, and it logs that they can't be turned off.Look at: I checked the startup log rather than hammering an endpoint. Anyone hosting a public server with
yarn devand noNODE_ENV=productionnow has no limits, where before they had them. It logs a warning at startup.🤖 Generated with Claude Code