-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Ensure dev server restart respects base
removal
#8027
Conversation
🦋 Changeset detectedLatest commit: 3e1a5a7 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@@ -1,5 +1,4 @@ | |||
import { escape } from 'html-escaper'; | |||
import { baseCSS } from './css.js'; |
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.
This is unrelated cleanup, but I was in this file so it made sense
if (settings.config.base !== '/') { | ||
viteServer.middlewares.stack.unshift({ | ||
route: '', | ||
handle: baseMiddleware(settings, logging), | ||
}); | ||
} | ||
// fix(#6067): always inject this to ensure zombie base handling is killed after restarts | ||
viteServer.middlewares.stack.unshift({ | ||
route: '', | ||
handle: baseMiddleware(settings, logging), | ||
}); |
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.
Actual change is just removing the if
check for settings.config.base !== '/'
Changes
base
middleware should always be injected, even if the base is set to the defaultbase
is removedTesting
Tested manually since it's HMR/restart behavior
Docs
N/A, bug fix only