Updating react-storefront to avoid fetch failures #19
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
markbrocato
approved these changes
Feb 19, 2020
markbrocato
added a commit
that referenced
this pull request
Feb 19, 2020
* Update example to use proxied next.js * Updated config * Updated package version * Use serverless offline for running prod builds locally * Update favicon * Updating react-storefront to avoid fetch failures (#19) * Add watcher to restart server when service worker changes (#18) * Add watcher to restart server when service worker changes * Update SW watcher to account for weird nodemon bug (remy/nodemon#951) Co-authored-by: Mark Brocato <[email protected]> * add caching * Revert routes * some cleanup Co-authored-by: kaarelkelk <[email protected]> Co-authored-by: Sigurður Gunnar Njálsson <[email protected]> Co-authored-by: Kevin Henderson <[email protected]>
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.
See: #20