-
-
Notifications
You must be signed in to change notification settings - Fork 454
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(fix) - Fix internal and graphcache/extras main path #733
Conversation
🦋 Changeset is good to goLatest commit: 73d2f3f We got this. This PR includes changesets to release 2 packages
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 |
Hi, I am having problems with 1.9.7 and it seems like this might solve it, just wondering if you think it will, or should I open a new issue?
Thanks |
@OriginalEXE you can make sure by trying out the build: @urql/core: "https://pkg.csb.dev/FormidableLabs/urql/commit/73d2f3f8/@urql/core" |
Thanks. How would I make sure that I am using that package? I don't have @urql/core dependency in my project, only I did try downloading the package from your url and replacing the Thanks |
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.
Would the urql/core exports need this change as well?
No, the purpose of this is to support webpack @wgolledge The problem is, for node to switch to |
That's published as |
Make the extension unknown so it can decide for itself what it likes the most, this is similar to https://github.com/FormidableLabs/urql/blob/master/packages/core/package.json#L21
Fixes: #732