Conversation
# Conflicts: # packages/vue-composables/src/use-shape.ts # packages/vue-composables/test/support/test-context.ts # packages/vue-composables/test/support/test-helpers.ts # pnpm-lock.yaml
added vue added as peerDependecy
…ables # Conflicts: # examples/vue/db/migrations/01-create_items_table.sql # examples/vue/package.json # examples/vue/src/App.vue # examples/vue/src/Example.vue # examples/vue/vite.config.ts # packages/vue-composables/src/use-shape.ts # pnpm-lock.yaml # website/.vitepress/theme/custom.css # website/.vitepress/theme/index.js # website/docs/integrations/vue.md # website/src/components/home/ReleaseBanner.vue
# Conflicts: # .tool-versions # pnpm-lock.yaml # website/.vitepress/theme/custom.css # website/docs/intro.md # website/src/components/home/ReleaseBanner.vue
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
3dyuval
force-pushed
the
vue-composables
branch
4 times, most recently
from
be7228e to
83ad831
Compare
3dyuval
force-pushed
the
vue-composables
branch
from
83ad831 to
017354e
Compare
|
Really nice work. Unfortunately, we're can't merge it into the mono repo since we don't want to expand the range of integrations we want to maintain. We'd be very happy to help with any feedback you need if you're willing to maintain it in a separe repo. |
|
@balegas I really dont mind maintaining it. How would we register it, under electric npm though? |
|
not under electric. We can point to it under our website under third-party clients. |
|
I see the concern around monorepo maintenance, but I'd push back gently on the docs. Even if it isn't under Electric The docs in this PR is an example of incremental Electric adoption, in native VueJS style for Vue developers. Its the entry point I'd expect to reactivity with shapes model, the solutions around the friction of no joins, its a well written documentation. As to the repo, pointing to a third-party link without context leaves a gap that'll show up as repeated questions in issues and Discord. A PR left hanging also loses the Vue developers who showed interest here... hard to re-engage that momentum later. Happy to scope this down to docs only , but curious how the team sees it? where would this PR land, and what's the expected governance around docs when the package lives externally? |
2 participants
Hello ElectricSQL!
I'm happy to contribute to both ElectricSQL and the Vue ecosystem with a new
packages/vue-composablespackage.First and foremost - full parity with
@electric-sql/react-hooks.Disclaimers
To be fully transparent, this was largely built with the help of Claude Code. That said, my experience as a front-end developer working with Vue 3 full-time for the last 3+ years shaped this into the tool I always wanted.
What does this PR adds?
packages/vue-composables
properties like data, isLoading, and error are directly
reactive
down via onUnmounted()
connections when multiple components use the same shape
mounts
works, matching the React hooks DX
examples/vue
A demo app showing ElectricSQL maintainer profiles synced
from Postgres. Includes a GitHub username lookup that
fetches a user's profile from the API, inserts them into
the database, and lets Electric sync the new row to the
UI automatically.
website/docs/integrations/vue.md
Docs page with sidebar navigation covering setup, usage
patterns, and API reference for the Vue composables.
Closes #3015
commits