fix: disable fsServe restrictions by default #3377
Merged
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.
Description
As discussions with the team, we decided to postpone the
fsServe
restrictions tov2.4.0
or later when we find the solutions to solve a few issues and make the logic more robust and well tested.This PR adding a new options
server.fsServe.strict
and set the default tofalse
, and disabling the restrictions by default. In the future versions of Vite, we will changeserver.fsServe.strict
totrue
when the restrictions issue are resolved.You can still opt-in this security change by
Additional context
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).