📦 TypeScript Application Template

📚 Summary

Professional Template with CI/CD-enabled, versioning with Semantic Release and Typedoc+VitePress documentation.

🧩 What's Included

Core Infrastructure

• ☑️ Node.js + TypeScript
• ☑️ Vitest (Unit Testing)
• ☑️ Semantic Release
• ☑️ GitHub Actions CI/CD
• ☑️ GitHub Actions GitHub Pages

Quality Assurance

• ☑️ BiomeJS (Linting/Formatting)
• ☑️ Husky + Lint Staged
• ☑️ Commitlint + Conventional Commits
• ☑️ CodeQL Scanning

Project Scaffolding

• ☑️ Docs: Contribution Guide & Code of Conduct
• ☑️ Husky Git Hooks
• ☑️ Automated CHANGELOG.md with Semantic Release
• ☑️ TypeDoc + Vitepress for Documentation Site

❓ When to Use This Template

Perfect for developers who need:

1. Zero-config TypeScript library setup
2. Automated docs with TypeDoc
3. CI/CD pipeline with GitHub Actions
4. Semantic versioning right out of the box

💡 Ideal for:

• Building npm packages
• Open source projects
• Enterprise-grade libraries

---

🤖 Automation Workflows

Workflow	Description	Trigger
0.test.yml	Runs unit tests	Push/PR to main or develop
1.create-pr.yml	Creates or updates a pull request from develop to main	Push to develop
2.deploy-docs.yml	Deploys documentation and coverage badge	After a successful release
3.release.yml	Generates changelog, tags, and releases	Push to main

---

🚀 Quick Start

npx degit heliomarpm/tsapp-template your-app
cd your-app
npm install

🛠️ Initial Setup

1. Replace template info:

   • Update name and description in package.json
   • Set version to 0.0.0 in package.json
   • Replace all references to tsapp-template and heliomarpm in package.json and README.md
   • Delete CHANGELOG.md

2. Configure GitHub repository:

   • Enable GitHub Actions (Settings → Actions → General)
   • Set up branch protection rules (optional)
   • Configure GitHub Pages for documentation

---

📈 Semantic Versioning

This template uses semantic-release for automated version management and package publishing. Version numbers are determined automatically based on commit messages:

Commit Message	Release Type	Example Version
revert(scope): message	Patch	1.0.1
fix(scope): message	Patch	1.0.1
feat(scope): message	Minor	1.1.0
BREAKING CHANGE: message	Major	2.0.0

📝 Commit Message Format

<type>(<scope>): <short summary>
│       │             │
│       │             └─⫸ Summary in present tense. Not capitalized. No period at the end.
│       │
│       └─⫸ Commit Scope: core|docs|config|cli|etc.
│
└─⫸ Commit Type: fix|feat|build|chore|ci|docs|style|refactor|perf|test

When a commit is pushed to main branch:

1. semantic-release analyzes commit messages
2. Determines the next version number
3. Generates changelog
4. Creates a git tag
5. Publishes the release to GitHub

Note: To trigger a release, commits must follow the Conventional Commits specification.

---

📦 Project Scripts

• npm run lint — run linter and fixer
• npm run format — run formatter
• npm run test — run unit tests
• npm run test:c — run unit tests with coverage
• npm run commit - run conventional commits check
• npm run release:test — dry run semantic release
• npm run docs:dev — run documentation locally
• npm run docs — build documentation and deploy

Generate Documentation Page

see TypeDoc Vitepress

• First time: npx vitepress init
• Documentation code base: npm run docs or npm run docs:dev

---

⚙️ Configuration Guide

🔐 Workflow permissions

For GitHub Actions workflows to create, edit, and manage Pull Requests via API (GitHub CLI or REST) and perform operations like push, release, and deploy, you need to configure the appropriate repository permissions.

1. Go to your repository's Settings → Actions → General
2. Go to section Workflow permissions
3. Set the permission level to Read and write permissions
4. Check on Allow GitHub Actions to create and approve pull requests
5. Click on "Save changes"

By default, the GITHUB_TOKEN token used in actions has read-only permissions. Enabling Read and write permissions allows you to create PRs, edit PRs, commit changes, and create tags/releases programmatically.

📌 Configuration alternatives

Replace the GITHUB_TOKEN with:

🔐 Option 1 — Classic Personal Access Token (PAT)

✅ Required permissions:

• repo (for read and write access to repositories)
• workflow (for interacting with GitHub Actions)

✅ Features:

• A single token can be used in any repository of the same user or organization
• Cannot restrict granular access to specific repositories or permissions (full access within the configured scope)

✅ How to use:

1. Create a Classic PAT in: GitHub Settings → Developer Settings → Personal access tokens → Tokens (classic)

2. Enable the scopes:

   • repo
   • workflow

3. Save the token as a secret in the repository:

   • Settings → Secrets and variables → Actions
   • Suggested name: PAT_TOKEN

4. Reference in workflow:

env:
  GITHUB_TOKEN: ${{ secrets.PAT_TOKEN }}

🔐 Option 2 — Fine-grained Personal Access Token (PAT)

✅ Required permissions:

• Contents: Read and write
• Actions: Read and write
• Metadata: Read-only
• (Optional) Bypass branch protections if you want to allow direct push even on protected branches

✅ Features:

• Allows you to restrict access to specific repositories at the time of creation
• Controls permissions with more granularity and security
• Needs to explicitly mark which repositories it will have access to
• Can be used in multiple repositories if configured to allow access to those repositories during token creation (either by selecting "All repositories" or manually selecting multiple)

✅ How to use:

1. Create a Fine-grained PAT in: GitHub Settings → Developer Settings → Personal access tokens → Fine-grained tokens

2. Set:

   • Repositories: select all required or check "All repositories"
   • Permissions:
     • Contents: Read and write
     • Actions: Read and write
     • Metadata: Read-only
     • (Optional) Bypass branch protections

3. Save the token as a secret in the repository:

   • Settings → Secrets and variables → Actions
   • Suggested name: PAT_TOKEN

4. Reference in workflow:

env:
  GITHUB_TOKEN: ${{ secrets.PAT_TOKEN }}

📌 Recommended Permissions Summary

Operation	GITHUB_TOKEN (read/write)	Classic PAT	Fine-grained PAT
Create/Edit Pull Request	✅	✅	✅ (Contents: RW)
Commit files to repository	✅ (if no branch protection)	✅	✅
Create releases and tags via API	✅	✅	✅
Bypass branch protection	❌	❌	✅ (if enabled)

⚠️ Note:
The built-in GITHUB_TOKEN in Actions respects all b>ranch protection rules, which prevents direct pushes to main if branch protection is configured.

Using a PAT or adjusting branch protection are the recommended solutions when automations require higher permissions.

For security, it is best to use Fine-grained PATs whenever possible, with specific permissions for the repositories and actions required.

---

📦 Dependencies

✅ Zero runtime dependencies
🔄 All devDependencies are pinned to latest stable versions

🤝 Contributing

We welcome contributions! Please read:

• Code of Conduct
• Contributing Guide

Thank you to everyone who has already contributed to the project!

Made with contrib.nn.

❤️ Support this project

If this project helped you in any way, there are several ways to contribute.
Help us maintain and improve this template:

⭐ Starring the repository
🐞 Reporting bugs
💡 Suggest features
🧾 Improving the documentation
📢 Share with others

💵 Supporting via GitHub Sponsors, Ko-fi, Paypal or Liberapay, you decide. 😉

📝 License

MIT © Heliomar P. Marques 🔝

---