In order to run the project we need the following software binaries installed on our development machines:
node>=16.7.0
npm>=8.0.0
docker>=20.10.12
supabase>=0.18.0
To install the application:
npm ci
To start a local copy of the app on port 3000
:
npm start
For running the test suite, use the following command. Since the tests run in watch mode by default, some users may encounter errors about too many files being open. In this case, it may be beneficial to install watchman.
npm test
You can request a coverage report by running the following command:
npm run test:coverage
A development preview can also be run from docker:
docker build -t open-sauced-template .
docker run -p 8080:80 open-sauced-template
Alternatively you can pull the production container and skip all builds:
docker run -dit -p 8080:80 ghcr.io/open-sauced/open-sauced
To check the code and styles quality, use the following command:
npm run lint
This will also display during development, but not break on errors.
To fix the linting errors, use the following command:
npm run format
A production deployment is a complete build of the project, including the build of the static assets.
npm run build
You can analyze the build by running the following command:
npm run build:analyze
We also have a script for updating .svg
files used in the project, you only need to run this if you add new assets:
npm run build:svgo
And one for .png
and .jpg
files:
npm run build:squoosh
Thanks to antfu/vite-plugin-inpesct we can always inspect the bundles in development by navigating to localhost:3000/__inspect/ in your browser.
We encourage you to contribute to Open Sauced! Please check out the Contributing guide for guidelines about how to proceed.
Got Questions? Join the conversation in our Discord.
Find Open Sauced videos and release overviews on our YouTube Channel.
MIT ยฉ Open Sauced