New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pin node-fetch version temporarily #870
Conversation
馃 Changeset detectedLatest commit: d05c1da The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
You're welcome! And thanks for the fix. By the way, Once confirmed, they can publish it and we can then release the constraint on this version. I will confirm on my end if I can; if you have a chance to confirm also that would be very helpful. |
Thanks @robrecord. If tests pass I think we can merge and release this so we don't depend on when |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 馃憤
Thanks Michal! |
Instructions for for less experienced users.
|
What:
Temporarily pin the version of
node-fetch
to 2.6.2. Fixes #868.Why:
Because
node-fetch
introduced a problem with an import in the 2.6.3 version that is breaking Frontity.How:
By removing the
^
of the version number for now.Tasks:
Unrelated Tasks
Additional Comments
Thanks to @robrecord for the catch 馃檪