-
Notifications
You must be signed in to change notification settings - Fork 6
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
Multiple Reactive libraries loaded. #15
Comments
I've tested forcing all deps to use "pnpm": {
"overrides": {
"@reactivedata/reactive": "0.2.2"
}
}, |
Almost gave up on svelte + yjs, thought it was server rendering issue. |
I am running into the same issue. 0.2.2 does not help. :/ |
Does clearing node_modules and possibly your lock files help? If not, does your lockfile show duplicate entries for any of the reactive or syncedstore libraries? |
@YousefED the problem appears to be due to @syncedstore/core depending on |
@YousefED I did all of that. I also set up a new CRA app and copied your todo app. even then I had the error. When I used yarn resolutions to make sure Using the same code in Next did not work, even with the resolution because both versions were installed. |
Could you see if you have the same issue with version 0.6.0-alpha.0 (just
published)?
…On Wed, Aug 23, 2023 at 1:27 PM Andre Zimpel ***@***.***> wrote:
@YousefED <https://github.com/YousefED> I did all of that. I also set up
a new CRA app and copied your todo app. even then I had the error. When I
used yarn resolutions to make sure @reactivedata/reactive was 0.2.2
(currently 0.2.0) it worked in CRA.
Using the same code in Next did not work, even with the resolution because
both versions were installed.
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC2BWLCAMJZDNSTXVQKI5DXWXSKXANCNFSM6AAAAAA2M6M5KY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I'm seeing warnings after upgrading @syncedstore dependencies
I guess this is because of the versions of
@reactivedata/reactive
being out of sync. See thepnpm why
output below:The text was updated successfully, but these errors were encountered: