Create a new Astro integration to handle an Astro-DB like setup

[apollo-git-bot]

but utilizing Kysely under the hood. This will allow users to also benefit from our new Kysely DB package when using Astro. Astro plans to deprecate Astro-DB in the future, so we should attempt to provide a smooth migration path for our users before that happens.

---

studiocms/packages/@withstudiocms/kysely/src/index.ts

Lines 12 to 16 in e359a69

	// TODO: Create a new Astro integration to handle an Astro-DB like setup
	// but utilizing Kysely under the hood. This will allow users to also
	// benefit from our new Kysely DB package when using Astro.
	// Astro plans to deprecate Astro-DB in the future, so we should attempt
	// to provide a smooth migration path for our users before that happens.

---

This issue was generated by todo-issue based on a TODO comment in e359a69.

[jesseagleboy]

Astro plans to deprecate the DB integration for their framework?

[Adammatthiesen]

Astro plans to deprecate the DB integration for their framework?

@jesseagleboy That was only meant as a short summary 😅

They (we, I am also an Astro Maintainer) have not officially came to a decision on this topic, but it was discussed, that IF Astro was to decide on deprecation, is there a viable community alternative, and we (StudioCMS) are the only ones who really know how @astrojs/db works internally (mainly since I am one of the people who help maintain that package and it's docs) so we are preparing our implementation that supports multi-dialect for the possible eventuality that we take-over the duties of the Astro DB integration. (AstroDB is physically locked to sqlite/libsql due to how drizzle works under the hood)

[jesseagleboy]

I think this also answered my question I had on your blog post about what it meant for Astro if maintainers of Astro dropped the current database integration and replaced it with Kysely. Seems like there's consistency in place.

[Adammatthiesen]

I think this also answered my question I had on your blog post about what it meant for Astro if maintainers of Astro dropped the current database integration and replaced it with Kysely. Seems like there's consistency in place.

Yeah, if i was to just re-write @astrojs/db that would result in a very massive, and breaking update... sometimes it's better to teach people a new name with a fresh interface... or let them DIY it themselves, since Astro docs do include instructions for common ORMs... instead of trying to get a full code-mod or something going...

We should also be able to build a import-export migration system for it. Similar to how i built @studiocms/migrator for StudioCMS data migrations (but probably without the fancy UI 🤣 )