We are using semantic-release to create npm releases based on the commit history.
This requires that you write your commits following the Angular Commit Message Conventions
Here is an example of the release type that will be done based on a commit messages:
Commit message | Release type |
---|---|
fix(pencil): stop graphite breaking when too much pressure applied |
Patch Release |
feat(pencil): add 'graphiteWidth' option |
|
perf(pencil): remove graphiteWidth option BREAKING CHANGE: The graphiteWidth option has been removed. The default graphite width of 10mm is always used for performance reasons. |
See Semantic release docs for more details
This repo provides the @cotype/core
package
internally we have two other packages: client and demo
- demo: an example/dev configuration for the server
- client: the frontend which is bundled within the server releases
To bootstrap the project and start a development server do the following:
npm install #once
npm start
When the server is started for the first time, the necessary tables are created and an inital admin user is created with the following credentials:
Email: [email protected]
Password: admin