fix: make resolveConfig() concurrent safe
#9224
Merged
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
brillout
force-pushed
the
fix/resolveConfig
branch
from
df26684
to
afc9d99
Compare
brillout
force-pushed
the
fix/resolveConfig
branch
from
afc9d99
to
f8dc0bd
Compare
antfu
approved these changes
Jul 19, 2022
brillout
added a commit
to brillout/vite
that referenced
this pull request
Jul 19, 2022
9 tasks
patak-dev
approved these changes
Jul 19, 2022
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Description
Makes
resolveConfig()concurrent safe.Additional context
It's a blocker for
vite-plugin-vercel.What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123).