Make frontend asset watcher build sequentially #1626
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
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.
Aim
I was running in to this issue locally; parcel-bundler/parcel#8165
The issue I was finding was that caseworker assets were being built, but exporter asset builds were consistently failing with the above issue.
Essentially, frontend asset watcher was concurrently building exporter and caseworker assets. This triggered an issue where both processes were writing to the parcel DB at the same time. I've adjusted things so that the assets are initially built in sequence before the watch part happens concurrently. This fixed the issue.
LTD-