v0.1.2 is not compatible with zero 0.17

[arv]

Zero 0.17 introduced a refCountMap parameter to applyChange.

However, I was not aware that Vue wrapped the data in Proxy objects. Therefore the refCountMap is not working as expected.

I've change Zero to not use a WeakMap and instead add the ref count to the actual entries. Once that is released zero-vue should work like it did in v0.1.1.

For now there are 3 options:

• Change the peer dependency version to not support zero 0.17
• Do what Solid did and a custom RefCountMap that unwraps the proxies.
• Wait until next zero release

[tantaman]

Would zero-vue v0.1.1 work with zero 0.17?

[saschwarz]

@arv just to clarify: for option 3 wait until the next zero release and revert the refCountMap changes made in zero-vue 0.1.2.

[saschwarz]

Would zero-vue v0.1.1 work with zero 0.17?

I don't think so because 0.17's api requires passing the refCountMap. It sounds like zero-vue 0.1.1 would work with the next zero release.

[arv]

The plan for now is to ask people to use a canary until 0.18 is fixed.

One of us will create a canary today or tomorrow.

[arv]

I pushed a canary called @rocicorp/zero@0.18.2025031800

Let me know if that works for you?

[saschwarz]

@arv using these versions:

I get this error on update:

Reverting zero-vue to 0.1.1 it works without errors.