turn off auto reload of admin page in production #124
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
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.
Some cloud providers don't use the same build machines in prod as dev, and in some cases don't cache the header files for SWC. This results in some deploys failing as the app tries to run webpack in prod which causes runtime failures.
Separately, running this causes more memory usage, which may make new developers believe their minimum requirements and thus spend in the cloud is higher than it actually needs to be. For example, you can run this on the free tier of some services such as render.com but couldn't if you are trying to run webpack on the deployed machine.