chore: re-build fsevents and node-gyp of lockfile to fix development install #154
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
|
cc @bsneed / @colinking |
colinking
added a commit
that referenced
this pull request
Dec 1, 2020
This PR extends #154 (comment) to upgrade jest, which ends up upgrading the dependencies that caused those issues. It also upgrades typescript and eslint to resolve various issues associated with upgrading jest. Looks like this also replaces: #155 This appears to resolve #153 for me. cc @bryantbiggs @alexmarchis-toptal: let me know if this fixes your problems. Thanks for originally digging into this, @bryantbiggs!
|
Closing in favor of #156 |
# 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.
yarnyou will encounter a number of errors related to node-gyp and fsevents. this change fixes those errors by removingnode-pre-gypandfseventsfrom the lockfile and re-runningyarnto allow the dependency tree to re-resolve itself correctlyFixes #153