@gjuchault/typescript-service-starter

Typescript Service Starter

Yet another (opinionated) typescript service starter template.

Opinions and limitations

1. Tries to follow Domain Driven Development
2. Config should not default to either development or production (link)

And extends the ones from typescript-library-starter

1. Relies as much as possible on each included library's defaults
2. Only rely on GitHub Actions
3. Do not include documentation generation

Getting started

1. git clone [e-mail]:gjuchault/typescript-service-starter.git my-project
2. cd my-project
3. npm install
4. npm run setup

Or click on Use this template button on GitHub!

To enable deployment, you will need to:

1. Setup NPM_TOKEN secret in GitHub actions (Settings > Secrets > Actions)
2. Give GITHUB_TOKEN write permissions for GitHub releases (Settings > Actions > General > Workflow permissions)

Features

Node.js, npm version

Typescript Service Starter relies on volta to ensure node version to be consistent across developers. It's also used in the GitHub workflow file.

Typescript

Leverages esbuild for blazing fast builds, but keeps tsc to generate .d.ts files. Generates two builds to support both ESM and CJS.

Commands:

• build: runs typechecking then generates CJS, ESM and d.ts files in the build/ directory
• clean: removes the build/ directory
• type:dts: only generates d.ts
• type:check: only run typechecking
• type:build: only generates CJS and ESM

Tests

typescript-service-starter uses ava and esbuild-register so that there is no need to compile before the tests start running. The coverage is done through nyc.

Commands:

• test: runs ava test runner
• test:coverage: runs ava test runner and generates coverage reports

Format & lint

This template relies on the combination of eslint — through typescript-eslint for linting and prettier for formatting. It also uses cspell to ensure spelling

Commands:

• format: runs prettier with automatic fixing
• format:check: runs prettier without automatic fixing (used in CI)
• lint: runs eslint with automatic fixing
• lint:check: runs eslint without automatic fixing (used in CI)
• spell:check: runs spellchecking

Releasing

Under the hood, this service uses semantic-release and commitizen. The goal is to avoid manual release process. Using semantic-release will automatically create a github release (hence tags) as well as an npm release. Based on your commit history, semantic-release will automatically create a patch, feature or breaking release.

Commands:

• cz: interactive CLI that helps you generate a proper git commit message, using commitizen
• semantic-release: triggers a release (used in CI)