fix: Use sequential and post order for vite artifact deletion#568
Merged
Conversation
Contributor
Author
|
No other plugins are considered, currently only for reference |
sequential and post order for vite artifact deletion
Contributor
Author
Too fast , Hope there are no bugs 🥲 By the way, it seems that my electron vite project(used vite-plugin-electron) has the same problem( Triggered multiple Thanks again |
This was referenced Aug 28, 2024
This was referenced Sep 5, 2024
This was referenced Sep 14, 2024
This was referenced Sep 21, 2024
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
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.
Sometimes writeBundle is executed before the upload task, need to ensure the order of code execution