Skip to content

Latest commit

 

History

History
225 lines (174 loc) · 7.93 KB

README.md

File metadata and controls

225 lines (174 loc) · 7.93 KB
Raw

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 && pnpm i
# (optional) playwright is required for end-to-end testing
bunx 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 pnpm 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

To update the packages to their latest versions in package.json

pnpm up --latest -r
pnpm audit --fix

Format

Format and lint code

turbo format
turbo format --filter=!'@console'
turbo lint

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)
./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
pnpm publish