jason•4w ago

I installed Convex on 2 apps today: 1.)

I installed Convex on 2 apps today: 1.) React Router v7 & 2.) SvelteKit. React Router went smoothly. Svelte was ok, but room for improvement... 🧵

6 Replies

jasonOP•4w ago

1. Step 3 of the SvelteKit Quickstart does not say where to save the convex.json file--in src, in convex, my monorepo root, or the SvelteKit root? Mentioning "...in the SvelteKit project root" would clarify this. https://docs.convex.dev/database/writing-data 2. The React client lib is available via convex/react, but Svelte is available convex-svelte. Possible to just make it available at convex/svelte too? Less guessing and more of "that just makes sense". 2. Similarly, React has useQuery and useMutation--beautiful. But Svelte has:

import { useConvexClient, useQuery } from "convex-svelte";
const getTasks = useQuery(api.tasks.get, {});
const client = useConvexClient();
client.mutation(api.tasks.createTask, { text: "Hello, world!" });

import { useConvexClient, useQuery } from "convex-svelte";
const getTasks = useQuery(api.tasks.get, {});
const client = useConvexClient();
client.mutation(api.tasks.createTask, { text: "Hello, world!" });

If it were refactored to mirror convext/react's, it'd be more intuitive. 4. The example mutation in the convex-svelte README is broken b/c it's missing proper imports. I submitted an issue. https://github.com/get-convex/convex-svelte Thanks for including Svelte in the docs!

erquhart•4w ago

This is good feedback 🙌 Note there's a dedicated #sveltekit channel too (in case it's helpful)

jasonOP•4w ago

oh good to know!

ballingt•3w ago

Thanks @jason! No convex.json file is strictly necessary, but it's nice if you want to put convex functions in an unusual spot like src/convex/. Re 2), we want to have fewer peer dependencies in the convex npm package so would rather keep this separate, but helpful to hear, it's possible we could combine these. We don't want them autocompleting if you're not using Svelte though. Thanks so much for fixing the broken example.

jasonOP•3w ago

Thanks. 1.) I understand, just sharing where, I as a new user, got a little confused with the instructions ambiguity about where to save the file b/c if instructions said in the SvelteKit project root that'd remove the ambiguity. 2.) Makes sense on the peer deps. Having designed DX focused stuff and noticing Convex seems to care a lot about it too, just noting the inconsistency I found. Inverting the suggestion and extract all client libs into their own deps with similar naming would achieve consistency too convex-svelte, convex-react, etc. Just my unsolicited 2c. I try to share feedback when learning a new product with fresh eyes. Works either way 👍

ballingt•3w ago

This is great, thanks for sending! Also if you run into Svelte inconveniences or missing things feel free to open more issues on that repo. Yeah I think splitting these out is a good idea, we've got that on the list. Right now when using the react-query bindings for example you can accidentally import the wrong useQuery since Convex has one and so does React Query, would be great to make having the React hooks an opt-in.

I installed Convex on 2 apps today: 1.)

Did you find this page helpful?