sql-examples VS vuesion

If you decide to do this we should put it on database.dev - i'm sure it would be very popular

database.dev fills the same role for PostgreSQL as npm for JavaScript or pip for Python, it enables publishing libraries and applications for repeatable deployment. Our goal is to create an open ecosystem for packaging and discovering SQL.

Supabase just wrapped up their Launch Week 7 with a ton of incredible features. This includes an AI assistant that was added to their premium platform. It is aware of your database design and can help you when creating more complex SQL queries. I'm even more thrilled by their most recent releases of outstanding open source projects, such as the PostgreSQL package manager database.dev. dbdev serves the same purpose for PostgreSQL that npm does for JavaScript. It gives your PostgresSQL database incredibly easy access to packages that give your DB superpowers like full-text search or one-time-only-read data access à la Snapchat. The best thing is that dbdev can load any PostgreSQL instance that has the required fundamental extensions, independent of the Supabase platform. Again, the code is open source. I can't wait to see where this project goes in the future, and I have no doubt that we will soon be able to utilize a lot more fantastic libraries. Like Brandon Roberts puts it:

hi hn!

supabase engineer and author of dbdev here

happy to answer questions

If you're looking for a next step after reading the article, checkout the available packages on https://database.dev

(shameless plug) https://database.dev/olirice/asciiplot is a fun one to play around with if you have some queries that could use optimization

I'm really looking forward to opening dbdev up to community packages in the coming weeks

https://database.dev/ Database for SQL commands - great for backend engineers!

If you - find it useful, please spare a 🌟 at the Github Repo If you - found any issue/bug, create issues is much appreciated. If you - wanted to contribute the SQL scripts, PR is even more welcomed!

I use them in all of my input components: https://github.com/vuesion/vuesion/tree/next/src/components/input-and-actions

I can provide you with my knowledge about Vue 2/nuxt2: https://github.com/vuesion/vuesion and Vue 3/nuxt3: https://github.com/vuesion/vuesion5

https://github.com/vuesion/vuesion or for nuxt3/vue3: https://github.com/vuesion/vuesion5

I have a repo with Vue2 (Nuxt.js 2) + composition api and storybook: https://github.com/vuesion/vuesion

https://github.com/vuesion/vuesion has GQL setup included

one exception is using plugins like i18n, they can also be used inside presentational components because they are pretty easy to integrate (no specific set of configuration per use-case) into storybook and tests. if you want to see my setup, go to https://github.com/vuesion/vuesion

I have a nuxt2 boilerplate that uses composition api already. Should hopefully be easy to migrate to nuxt3 later this year: https://github.com/vuesion/vuesion. I hope it helps you to make a decision

We maintain a (nuxt) template project that new projects are forked from. It contains all the settings and libraries that we minimally need for an app. I think it's important to have your own template project, rather than use someone else's.

Give this a shot: https://github.com/vuesion/vuesion

I maintain a reference project as boilerplate here: https://github.com/vuesion/vuesion. let me know if you have any questions.