feat: allow ssrRef to work outside of setup

[danielroe]

This PR removes the custom prefetching we were doing (via redefinition of onServerPrefetch, and instead uses a transparent proxy for the ssrRef on server-side to update the state every time it is changed.

see #40

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nuxt-community/composition-api/c9na82xy3
✅ Preview: https://composition-api-git-no-setup-ssrrefs.nuxt-community.now.sh

[danielroe]

Would value your thoughts @mathe42. Do we lose anything by doing it this way?

[mathe42]

Yes we can not track deep changes.

[danielroe]

@mathe42 Yes, of course. Good catch. Thoughts on amended proxy approach?

[mathe42]

This will break IE11

[mathe42]

I think we can add a option to use Proxies and fallback to the onServerPrefetch stuff.

Outside Setup when Proxies allowed use it else always send state to client...

[danielroe]

@mathe42

This will break IE11

The proxy code won't be in the client bundle; it's just server-side.

Outside Setup when Proxies allowed use it else always send state to client...

It should only send state after something is assigned to the proxy. So

// This shouldn't be sent
const a = ssrRef('init')
// But this now will be
a.value = 'init'

[mathe42]

Nice 👍

Does this mean we need Node Version >= x? => change package.json

[mathe42]

Node >= 6.0

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy

[mathe42]

Node >= 6.0

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy

But nuxt needs later versions:

https://github.com/nuxt/nuxt.js/blob/dev/distributions/nuxt/package.json