Switch to vscode-chokidar [Updated] #834
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
|
I am trying to build the package and getting this output from webpack.
|
|
Just fixed it. Making a new PR with the change. |
1 task
shanalikhan
pushed a commit
that referenced
this pull request
Apr 9, 2019
* Switch to vscode-chokidar * Include vscode-fsevents as an external
shanalikhan
pushed a commit
that referenced
this pull request
Apr 18, 2019
* Switch to vscode-chokidar * Include vscode-fsevents as an external
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.
Short description of what this resolves:
This fixes issues with extension host being killed.
Changes proposed in this pull request:
vscode-chokidarpackage instead ofchokidarFixes: #827
How Has This Been Tested?
Tested by @WesCoder and @Spacebody
Checklist: