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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: consistent html handling between dev and preview #11289
fix: consistent html handling between dev and preview #11289
Changes from all commits
063ef79
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could add a middleware here to support rewriting
/foo
to/foo.html
. I didn't implement it because it wasn't supported in dev.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to add an option in
preview
to skip theshouldServe
and letsirv
handle it?.That would allow frameworks like îles to configure the
preview
to work in a way that is consistent with the deployment target (which might resolve/foo
to/foo.html
).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that is possible by injecting a middleware by the post
configurePreviewServer
hook, too.In that way, I think we can have the same behavior in dev by injecting that middleware by
configureServer
hook.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With dev server, these tests passes without this PR.
With preview server and without this PR, these tests resolved to
nested/index.html
->nested/index.html
nested
->nested/index.html
(changed, Inconsistent URL trailing slash behavior between dev and preview servers #6596)nested/
->nested/index.html
non-nested.html
->non-nested.html
non-nested
-> 404 (changed, Routing broken for preview with react-router-dom in 4.0.0-alpha.2 #10925)non-nested/
-> 404 (changed, Routing broken for preview with react-router-dom in 4.0.0-alpha.2 #10925)