Docs: Add sample code to use Kysely in Deno & manage migrations

[Sleepful]

Hello!

It took me a while to figure out this one, here I hope to make it easier to others.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
kysely	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 2, 2025 9:01pm

[Sleepful]

I can't see the details of the CI failing 😅

[Sleepful]

@igalklebanov hello 👋 do you think this documentation is helpful?

[igalklebanov]

I can't see the details of the CI failing 😅

Did you run your changes locally?

[Sleepful]

Oh yeah, I was using npm start and it didn't error. Now that I see your screenshot, I see that I should have been running npm run build to check.

I updated the PR:

• Fixed some links
• Added a /site/README.md where I mention that npm run build checks for correctness.
• Merged with master to reconcile the changes from your recent PR: https://github.com/kysely-org/kysely/pull/1035/files

[Sleepful]

I can continue updating with master branch, but first I will wait to get approval or feedback on the changes

[Thaigun]

Just letting y'all know that the example was useful fo me, in particular DenoMigrationProvider. 😌

[Sleepful]

hi @igalklebanov 👋 I don't see the CI checks going beyond "waiting", would you like to add this PR? Making it easier for Deno folk could drive up Kysely adoption

[igalklebanov]

Hey 👋

We appreciate the effort! Thank you very much! 🙏

I'm afraid it's out of scope for Kysely's docs to teach people how to use a specific runtime.

The migrations primitives we provide are an example implementation, and are optional. We also ship kysely-ctl now, that supports all runtimes, Deno included - weakening the need to write your own CLIs.

Deno supports Node.js APIs, so there's no true need for runtime-native.