Proposal: Update ts-invariant
#67
Closed
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
|
Update: This did not work when I shipped it to production :( |
|
Yeah confirmed this one 100% does not work, go with the removal |
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.
Related issue: #65
Just heard from @glasser at Apollo that the process.env bug has been solved in a recent
ts-invariantupdate: apollographql/invariant-packages#107 (comment)This PR updates the version of
ts-invariantto the latest (^0.7.3). I tested this via patch-package on my repo to confirm it fixes the issue we were seeing :)I'm indifferent as to if you choose to remove or update, I have a separate pr for removing
ts-invarianthere: #66