fix: Support refresh and livereload in serve when using routerMode history (#132) - #165
Closed
Peksa wants to merge 1 commit into
Closed
fix: Support refresh and livereload in serve when using routerMode history (#132)#165Peksa wants to merge 1 commit into
Peksa wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
|
Committed the package-lock.json file and amended the commit. Since I sillily deleted my fork I had to create a new PR: #166 |
Sorry, something went wrong.
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
2 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.
When using docsify serve on a site which uses routerMode: history and you either refresh the page or change the site, triggering a live reload, you usually get a 404.
With this, the node connect server will serve the index file for most requests, using npm package connect-history-api-fallback.
This should solve #132