Contributions are welcome and any help that can be offered is greatly appreciated. Please take a moment to read the entire contributing guide.
This repository uses the Feature Branch Workflow,
meaning that development should take place in feat/
branches, with the main
branch kept in a stable state.
When you submit pull requests, please make sure to fork from and submit back to main
.
Other processes and specifications that are in use in this repository are:
- Semantic versioning
- Conventional commits following the @commitlint/config-conventional config
- Prettier style guide
Ensure you have all prerequisites installed (including any optional ones), as noted in the prerequisites section of the readme file.
With those in place, you can fork the repository, clone it, and then run npm ci
to install all dependencies.
Make a copy of .env.template
in the root directory and rename it to .env
, configuring the environment variables in the file as required.
After cloning the repository and installing all the dependencies, there are several commands available for local development:
npm run build
- Runs esbuild to compile code into dist directorynpm run lint
- Lints everything in src directorynpm run jest
- Runs Jest over all tests in src directorynpm test
- Runsnpm run lint
andnpm run jest
togethernpm run start:dev
- Starts a development server with live reload
npm start
- Runs a production version. No live reload.
Documentation (both in markdown files and inline comments) should be written in British English where possible.
Titles and headings should use sentence-style capitalisation, where only the first letter of a sentence and proper nouns are capitalised.
Before submitting a pull request back to the main repository, please make sure you have completed the following steps:
- Pull request base branch is set to
main
. All pull requests should be forked from and merged back tomain
- Run
npm test
to check the code adheres to the defined ESLint style and that it passes the Jest tests - Run
npm run lint:prettier:fix
to run the Prettier code formatter over the code - Run
npm run lint:licenses
if adding or updating production dependencies to check they use permissive licenses
Steps 2. and 4. are automatically run by a pre-commit hook added by Husky.
Please file your issues here and try to provide as much information in the template as possible/relevant.