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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@proplan-utvikling/husky

v1.0.1

Published

Shared Husky git hook scripts for Proplan applications.

Readme

husky/

Git hook scripts for Node.js projects (Angular and Azure Functions).
Copy the hooks you need into your project's .husky/ directory.


Contents

| File | Git hook | Runs | | ------------------ | -------------------------------------- | ---------------------------------------------------- | | pre-commit | Before every commit | lint-staged — lint and format staged files only | | commit-msg | After writing the commit message | commitlint — validates Conventional Commits format | | pre-push | Before every push | npm test — full unit test run | | pre-merge-commit | Before a non-fast-forward merge commit | lint-staged — quality check on merged files |


Prerequisites

Install the required packages in your application repo:

# Husky and lint-staged (for pre-commit and pre-merge-commit hooks)
npm install --save-dev husky lint-staged

# commitlint (for commit-msg hook)
npm install --save-dev @commitlint/cli @commitlint/config-conventional

Setup

1. Initialise Husky

# Husky v9
npx husky init

# Husky v8
npx husky install

2. Add the prepare script to package.json

{
  "scripts": {
    "prepare": "husky"
  }
}

This ensures hooks are installed automatically after npm install.

3. Copy hook files

cp husky/pre-commit       .husky/pre-commit
cp husky/commit-msg       .husky/commit-msg
cp husky/pre-push         .husky/pre-push
cp husky/pre-merge-commit .husky/pre-merge-commit

Make them executable (Linux/macOS and WSL):

chmod +x .husky/pre-commit .husky/commit-msg .husky/pre-push .husky/pre-merge-commit

4. Configure lint-staged in package.json

{
  "lint-staged": {
    "*.{ts,html}": ["eslint --fix"],
    "*.{ts,js,json,html,scss,css,md}": ["prettier --write"]
  }
}

5. Configure commitlint

Create commitlint.config.cjs in your project root:

module.exports = { extends: ["@commitlint/config-conventional"] };

Accepted commit types: feat | fix | docs | style | refactor | perf | test | build | ci | chore | revert

Example valid commit messages:

feat(auth): add JWT refresh token support
fix: handle null response from API
chore(deps): bump eslint from 8.0.0 to 9.0.0

Husky v8 vs v9

The hook files default to Husky v9 (plain shell, no boilerplate). If your project uses Husky v8, uncomment the two lines at the top of each hook and remove the bare command:

# v8 form — uncomment these two lines
. "$(dirname -- "$0")/_/husky.sh"
npx lint-staged

# and remove this line
npx lint-staged

CI pipelines

In CI, Husky's prepare script must not attempt to install git hooks (there is no .git directory with write access on the build agent). Use the shared pipeline template to disable this automatically:

# In your azure-pipelines.yml job steps — place BEFORE npm ci
steps:
  - template: pipelines/templates/shared/husky.yml@infrastructure
    parameters:
      skipInCI: true # sets HUSKY=0 for all subsequent steps (default: true)
      runHooks: # optional: re-run specific hooks as CI quality gates
        - pre-commit #   runs sh .husky/pre-commit on the build agent

See pipelines/templates/shared/husky.yml for full parameter reference.