drop-in Svelte Themes

Drop In

A platform for building apps rapidly with Svelte 5, Svelte Kit and if you'd like Pocketbase or Zero. Includes a modern bespoke component template library and a next level CSS. Use as a starter kit or take just what you need, components and CSS.

Drop In 🛹

Drop-in to your new app. Get started in no time, your framework should do more for you.

NOTE

This is a WIP. In the near future, the primary template will be local first via Zero. The most usable and available template is the

Getting Started

  1. npx @drop-in/new your-app-name || pnpx @drop-in/new your-app-name
  2. cd ./your-app-name
  3. pnpm install || npm install
  4. Set ENV credentials
  5. (optional). npm run typegen || pnpm typegen must have all env credentials set to work

Templates

  • Lofi -> Will eventually be the main template. Hidden until Zero is released.
  • Base -> SvelteKit / Svelte 5 / PocketBase. CSR for app code, SSR for Site code

Features & Packages

  • Base CSS @drop-in/graffiti
    • Basic typography system
    • Grid System
  • Elements @drop-in/decks
    • Standards based simple toast system
  • Aliases and structure

Lofi Template

  • Automatic Zero / Svelte integration
  • Drizzle Schema for User Accounts
  • Auth @drop-in/pass
  • Email @drop-in/email
  • Zero Server baked in

PocketBase Template

  • Type generation via pocketbase-typegen
  • Auth guard & App guard functions
  • Packages dir & scaffolding cli for easy internal packages

Included Aliases

$lib: 'src/lib';
$routes: 'src/routes';
$state: 'src/state';
$types: 'src/types';
$utils: 'src/utilities';

Commands

make-package

Usage: npm run make-package

Follow the wizard to create a new package. This will add a new package starter to the local packages folder /src/packages. This will also add "@org-name/your-package-name": "workspace:^", to your package.json file

types

Usage: npm run types

Generate types for pocketbase to be used throughout project. Requires all env vars to be correctly set.

FAQ

Why no authenticated SSR?

The base template has two main route paths. SSR based with no auth or app code with auth. While you could have authenticated user data there are enough major differences in approach (ie not using server actions, cookie for auth token, .server.ts files, ect..) that having both in this codebase felt like it would make it too complex. Might make a 2nd template with full SSR.

Why no (insert styling library) included?

It's pretty trivial to add those yourself and I wanted to keep this as bare as possible style wise. Many projects have their own CSS needs and I want to respect that. I'd like to add a cli with alternate builds of this with more baked in UI if anyone is interested in helping.

Inspirations

  • Svelte Kit CLI code
  • Meteor

Top categories

Loading Svelte Themes