The seed you plant to grow your project.
If you have SSH setup on your account, run the following command:
$ git clone [email protected]:tcmbytes/project-seed.gitOtherwise, you may use the HTTPS version (might ask for username and password):
$ git clone https://github.com/tcmbytes/project-seed.gitChange the working directory to the repo directory:
cd project-seedIf you're developing on macOS, then run the setup-macos.sh script. It will install the system dependencies, project dependencies and the evironment for your app:
bash ./bin/setup-macos.shOtherwise, make sure to manually install Node.js and yarn on your machine before continuing with the development.
$ node --version
v16.19.1
$ yarn --version
1.22.4To install the project dependencies, run the following install command:
$ yarnTo configure the environment variables of your project, make sure to configure the environment variables in the .env file:
cp .example.env .envor copy the next lines into your .env file:
MY_ENV_VAR='MY_ENV_VAR'To start the project in development mode, run the following command from the root directoy of the project:
$ yarn devTo continuously watch for file changes and check for syntax errors, run the following command:
$ yarn dev:watchTo run the unit test, run the following command from the root directoy of the project:
$ yarn testTo continuously run the unit tests as you code, run the following command:
$ yarn test:watchThe generated tests reports are available in ./reports/test-results.html file.
To generate the coverage report for your app, run the following command:
$ yarn test:coverageThe generated report is available in ./reports/coverage directory.
To transpile the TypeScript files into JavaScript, run the following command from the root directoy of the project:
$ yarn buildTo build and start the transpiled project, run the following command from the root directoy of the project:
$ yarn startTo run type, linting and prettier checks on your project, run the following command from the root directoy of the project:
$ yarn check:allAlternatively, you can run the scripts independently:
$ yarn check:type
$ yarn check:lint
$ yarn check:prettierFuthermore, to check for project dependency cycles, run the following command from the root directoy of the project:
$ yarn check:dpdm