ahmadnassri/node-assert

Node.js assert with a little sugar

Node Lib Template

node library project template

Features

CI Automation

Using GitHub Actions

• release with conventional-commits & semantic-release
• publish to both npm Public Registry & GitHub Package Manager
• full history changelog in GitHub Releases
• automatic pull-requests for dependency updates using dependabot
• automatic merging of "patch" updates to dependencies using dependabot-auto-merge
• lint everything with mega-linter
• lint commit message format against Conventional Commits
• test on all LTS versions of Node.js
• run npm audit before releasing / testing to keep a higher security standard
• repositories are kept up to date using @ahmadnassri/action-template-repository-sync

Local Automation

Using Docker Compose

• lint everything with mega-linter
• test on all LTS versions of Node.js
• generate README using pandoc with a template

Usage

GitHub Templates

Automated through @ahmadnassri/action-template-repository-sync

1. create a repository from the template
2. clone locally
3. add secrets in GitHub Actions for NPM_TOKEN & GH_TOKEN
4. update colophon.yml, docs/README.md with info about the project

Note:
GH_TOKEN is required for action auto-merge, readme, release workflows

Local Automation

use Docker Compose to run tasks locally:

• docker compose run readme to regenerate README.md
• docker compose run test to run tests across all LTS versions of Node.js
• docker compose run lint to execute mega-linter locally

Note:
Your main README.md file is in docs/README.md, the file at root is generated using pandoc using the provided template.

You should run docker compose run readme after any change to docs/README.md and before commit / push

---

Author: Ahmad Nassri • Twitter: @AhmadNassri