npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@xtreamsrl/githooks

v1.1.0

Published

A Nx generator to help with pre-commit hooks setup.

Downloads

1

Readme

@xtreamsrl/githooks

A Nx generator which:

  • install the husky and commitlint packages
  • configure the husky package to run commitlint on commit-msg hook

The commitlint configuration can be customized on installation, choosing between the @commitlint/config-conventional and @commitlint/config-angular presets.

The following commitlint rules are configured:

  • type-enum: the commit type must be one of the following: build, ci, chore, docs, feat, fix, perf, refactor, revert, style, test;
  • scope-enum: the commit scope must be one of the following scopes all, release, scripts or one of the apps or libs names, eventually prefixed with lib or app;
  • scope-empty: the commit scope must never be empty.

Installation

npm install @xtreamsrl/githooks

Usage

Generator

Run the nx generator and follow the instructions:

nx generate @xtreamsrl/githooks

Update commitlint configuration

The commitlint configuration is generated once when the nx generator is executed. So it will includes in the admitted scopes the apps and libs names at the moment of the installation.

When a new app or lib is created, the commitlint configuration must be updated to include the new scope. To do that, update manually the .commitlintrc.json file, adding the new scope to the scope-enum rule.

Build

Run nx build githooks to build the library.

Run unit tests

Run nx test githooks to execute the unit tests via Jest.

Linting

Run nx lint githooks to execute the lint via ESLint.

Versioning

Export the GH_TOKEN environment variable with your GitHub token with at least the repo scope:

export GH_TOKEN=<YOUR_PERSONAL_GH_TOKEN>

Then run the following command:

lerna version

The GH_TOKEN is needed to push the version commit and tag to the remote repository and to create the release on GitHub.

For general information about the versioning process, please refer to the root Readme Versioning section.

Publishing

Update your local .npmrc file to include the following lines:

@xtreamsrl:registry=https://registry.npmjs.org/
//registry.npmjs.org/:_authToken=${NPM_TOKEN}

The ${NPM_TOKEN} placeholder is a npm personal access token publish permissions on the @xtreamsrl organization. It can be treated as placeholder to replace with the actual token value, or you can set it as an environment variable:

export NPM_TOKEN=<YOUR_PERSONAL_NPM_TOKEN>

Then run the following command:

npm run lerna-publish

Who we are