This repository was archived by the owner on Jun 2, 2026. It is now read-only.
Fix npm run watchreact initial build bug#233
Merged
Merged
Conversation
…older already exists, and if not then create it first before setting up the watchers
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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:
Improved the npm run watchreact command:
Issue:
Resolves the error that occurs when users run
npm run watchreactfor the first time. The issue occurs because the watchers are set up at the same time. The second watcher (which uses tsup) fails because it is looking for the src2 directory to watch, which does not exist yet as it is being built for the first time by the other watcher (nodemon).