Not An Issue - but more of confirmation - Does this work with sveltekit?

[MelodicCrypter]

Does this still working on the current version of Sveltekit? It seems last update was more than 6+months ago.

[idc77]

I also wonder, but maybe change the title of the issue to reflect the actual question, "Does this work with sveltekit?"

[idc77]

Well, if you've checked the examples dir, there's a sveltekit dir

[MelodicCrypter]

Well, if you've checked the examples dir, there's a sveltekit dir

I see. But the examples and even the documentation is still based on the Sveltekit before version 1. For sure, you are aware of the breaking changes of version 1 of Sveltekit. Just making sure that the author is also active or aware of the sveltekit changes.

[binaryme]

It does work, I just configured it this morning and everything working smoothly.

[Emmanuel-Melon]

It does work, I just configured it this morning and everything working smoothly.

The documentation isn't very helpful when it comes to deciding whether to create a single instance for the app or use multiple instances. It's also unclear where to set the client, and the example only covers a single page. So, if I have multiple pages, would I need to set it for each one, including +layout.svelte?

For instance, the React client lets you wrap your components in ApolloProvider instance.

[MelodicCrypter]

It's been a year now (since last commit), so I switched to @urql/svelte . I like the simplicity of URQL.