Closed rcbevans closed 9 months ago
For anyone running into this issue, adding the following to my root package.json
forced yarn to resolve all resolutions of @reactivedata/reactive
to 0.2.0
, including @reactivedata/react
. This resolved the reactivity version mismatches and the app is back to behaving as it should with reactive elements updating as they change.
"resolutions": {
"@reactivedata/reactive": "0.2.0"
}
"@reactivedata/reactive@0.2.0", "@reactivedata/reactive@^0.2.0":
version "0.2.0"
resolved "https://registry.yarnpkg.com/@reactivedata/reactive/-/reactive-0.2.0.tgz#1d370724bb0e3599b96b768bee96099f9326ed23"
integrity sha512-qWmVSmUrjKHBiD+ZS8TxNNzyk9J6rbcZSZJgcnKQpTLwORZoWuX5pYbl07aU0kzXGLaaVX2O/ZW+SZaBjRQW3g==
@rcbevans could you see if syncedstore versions 0.6.0-alpha.0 work for you? If so, I'll ship those fixes
Give it a try and let you know.
Give it a try and let you know.
Thanks! Keep me posted :)
Sorry for the delay. Yes the updated package.json dependency versions in 0.6-alpha resolve the version conflict.
Recently I noticed a firehose of errors in the console about reactivity coming from syncedstore.
The basic functionality seems to be ok (I can store data in reactive arrays on a synced store, but reactivity seems to be broken, so after pushing items into the array, the UI no longer reactively rerenders until the host component rerenders.
Looking in yarn.lock I see
I believe this is because
@reactivedata/react@0.2.1
loosely depends on"@reactivedata/reactive" "^0.2.0"
which is resolving to"@reactivedata/reactive" "0.2.2"
, but@syncedstore/core@^0.5.2
strictly depends on"@reactivedata/reactive" "0.2.0"
Changing the
@syncedstore/core
package.json to depend on^0.2.0
should fix the issue I think.