How to implement a data access layer pattern in SvelteKit?

This page summarizes the projects mentioned and recommended in the original post on /r/SvelteKit

CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  1. svelte-headlessui

    HeadlessUI components for Svelte (by CaptainCodeman)

    You mention YAGNI, but I think the bigger blocker is "Don't reinvent the wheel" - which I think is the most misunderstood bit of programming advice out there. In my SvelteKit app, I am not using a "UI Framework" that provides components to me. I don't need to. Svelte is simple enough that I can build almost anything myself. I've looked at Skeleton's source code, and their components on average are not better than versions I have rolled myself. There are a few cases where it's better to use a framework. Sliders, for instance, have a lot of edge cases. So I use Swiper for carousels. But even then, I could build a working basic slider (that doesn't address the numerous edge cases) myself in an hour. The other case is Headless UI but even there, I disagree with how he implemented some things and it's possible to roll your own Svelte Headless UI just from Tailwind's source.

  2. CodeRabbit

    CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

    CodeRabbit logo
  3. Swiper

    Most modern mobile touch slider with hardware accelerated transitions

    You mention YAGNI, but I think the bigger blocker is "Don't reinvent the wheel" - which I think is the most misunderstood bit of programming advice out there. In my SvelteKit app, I am not using a "UI Framework" that provides components to me. I don't need to. Svelte is simple enough that I can build almost anything myself. I've looked at Skeleton's source code, and their components on average are not better than versions I have rolled myself. There are a few cases where it's better to use a framework. Sliders, for instance, have a lot of edge cases. So I use Swiper for carousels. But even then, I could build a working basic slider (that doesn't address the numerous edge cases) myself in an hour. The other case is Headless UI but even there, I disagree with how he implemented some things and it's possible to roll your own Svelte Headless UI just from Tailwind's source.

  4. next-auth

    Authentication for the Web.

    So it pushes people with limited backend experience into the arms of Supabase, Pocketbase, Whateverbase and companies like Netlify and Vercel. And then there's the rise of stuff like [Auth.js](https://authjs.dev/)

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Next.js and Next-Auth V5: Guide to Social Logins(OAuth)

    3 projects | dev.to | 23 Jan 2025
  • Implementing Authentication with Clerk in Next.js

    1 project | dev.to | 14 Oct 2024
  • GET, POST, PUT & DELETE with Next.js App Router

    2 projects | dev.to | 31 Aug 2024
  • Some packages are no longer installable after test command is removed

    6 projects | news.ycombinator.com | 29 Jul 2024
  • Enterprise-Level Authentication in a Containerized Environment for NextJS 13

    2 projects | dev.to | 16 Jun 2024