spectacular Svelte Themes

Spectacular

Sweet & Powerful SvelteKit Project Template https://spectacular-console.vercel.app/ https://spectacular-docs.vercel.app/ https://spectacular-web.vercel.app/

#flowbite#graphql#hasura#houdini#pnpm#postgresql#superforms#sveltekit#turborepo#mswjs
Demo Download

Spectacular

Spectacular is a full-stack Turborepo template project with SvelteKit meta-framework all working in harmony and sharing packages.

Tech Stack

Features

Experementing

Setup

cd ~/Developer/Work/SPA
git clone https://github.com/xmlking/spectacular.git
cd spectacular && bun install
# (optional) playwright is required for end-to-end testing
bun x playwright install
# (optional) add git-commit-hooks
cog install-hook --all

Environment Variables

By default, the dev server (dev command) runs in development mode and the build command run in production mode.
This means when running turbo build, it will load the env variables from .env.production if there is one:
Use .env.local to override environment variables in .env (secrets like API keys) for local development.

Developing

Once you've cloned the project and installed dependencies with bun i, start a development server:

Start local Hasura

# stat all services in background and show logs
make up # for first time use `make boot` then `make up`
# this will start all services with default profile + services with `all` profile.
make up PROFILES=all
# verify status/health of services
make ps
# shotdown all services
make down
# DANGER: run this if you want to reset database and other persistent volumes
make teardown
# verify if docker `compose` getting correctly resolved application config from .env and .secrests files
make check
make check PROFILES=all,optional
# ssch to a container to debug
#make exec-<target>
make exec-hasura
make exec-auth

Start apps/console

turbo run console#dev

# or use `--log-order=stream` to disable TUI
turbo --filter=console --log-order=stream dev

# or start the server and open the app in a new browser tab
turbo run console#dev  -- --open 

# run in debug mode
turbo run console#dev:debug

# run with a custom inline config
# inline environment variables has higher precedence than ones loaded from .env and .env.local files
PUBLIC_NHOST_GRAPHQL_URL=api.mycompany.com:443 turbo dev

Maintenance

Update

Display outdated dependencies:

# Display outdated dependencies globally
bun outdated -g
# Display outdated dependencies in the current workspace.
bun outdated
# Display outdated dependencies in the web workspace.
bun outdated -F web
bun outdated -F docs
bun outdated -F @repo/utils
bun outdated -F @repo/mastra
# Use --filter to include more than one workspace.
bun outdated --filter="*"

Update package dependencies to latest version:

# To update global dependencies 
bun update --latest -g 
# To update dependencies to latest for each workspace:
cd apps/web
bun update --latest
# (Or) upgrade interactively
bun update --interactive
bun update -i --latest

To debug why specific dependency was added:

bun why recharts

Format

# format all packages
turbo run format
# format root
turbo run format:root

Lint

# lint all packages
turbo run lint
# lint root
turbo run lint:root

Testing

Unit/Component Tests

turbo test

turbo test:ui
#Then, you can visit the Vitest UI at http://localhost:51204/__vitest__/.

# test coverage
turbo test:coverage

# updating Snapshots
bunx vitest -u

# test specific folder
bunx vitest apps/web/src/lib/utils
(or)
bun node_modules/.bin/vitest run apps/web/src/lib/utils

E2E Tests

turbo test:e2e

Building

To create a production version of your app:

turbo build
# run build
turbo run console#dev:build
turbo --filter=console... build
turbo --filter=console... --dry build
turbo --filter=console... --graph build

Run from the local build directory:

NODE_ENV=production \
PUBLIC_NHOST_GRAPHQL_URL=api.mycompany.com:443 \
node build

# (optional) pass ORIGIN when using `adapter-node` build
HOST=127.0.0.1 \
PORT=4000 \
ORIGIN=https://my.site \
node build

You can preview the production build with turbo run console#preview.

To deploy your app, you may need to install an adapter for your target environment.

Release

after checking-in all your changes, bump the VERSION and build the docker image.

# dry-run
cog bump --auto --dry-run
# this will bump version in package.json and create git tag and commit.
cog bump --auto

Libs

To build and publish libs

turbo build --filter=lib...
cd package
bun publish

Top categories

tailwinddaisyuiadmin templatepopupmdsvexportfolioblogformecommerceuicarouselauthdarkseoimagerouting
Loading Svelte Themes