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

eslint-plugin-handlebars

v1.0.4

Published

Lint Handlebars templates

Downloads

131

Readme

eslint-plugin-handlebars

Lint Handlebars templates

Installation

You'll first need to install ESLint:

npm i eslint --save-dev

Next, install eslint-plugin-handlebars:

npm install eslint-plugin-handlebars --save-dev

Usage

In your configuration file, import the plugin eslint-plugin-handlebars and add handlebars to the plugins key:

import { defineConfig } from "eslint/config";
import handlebars from "eslint-plugin-handlebars";

export default defineConfig([
  {
    plugins: {
      handlebars,
    },
  },
]);

Then configure the rules you want to use under the rules key.

import { defineConfig } from "eslint/config";
import handlebars from "eslint-plugin-handlebars";

export default defineConfig([
  {
    plugins: {
      handlebars,
    },
    rules: {
      "handlebars/rule-name": "warn",
    },
  },
]);

Configurations

| | Name | | :-- | :------------ | | ✅ | recommended | | 🔒 | strict |

Rules

💼 Configurations enabled in.
✅ Set in the recommended configuration.
🔒 Set in the strict configuration.
🔧 Automatically fixable by the --fix CLI option.

| Name                    | Description | 💼 | 🔧 | | :--------------------------------------------------------------- | :---------------------------------------------------------------- | :---- | :-- | | block-spacing | Enforce consistent spacing around Handlebars blocks | ✅ 🔒 | 🔧 | | consistent-quotes | Enforce consistent quote style in Handlebars expressions | ✅ 🔒 | 🔧 | | expression-spacing | Enforce consistent spacing around Handlebars expressions | ✅ 🔒 | 🔧 | | indentation | Enforce consistent indentation in Handlebars templates | ✅ 🔒 | 🔧 | | no-missing-closing-tag | Validate that Handlebars blocks have matching closing tags | ✅ 🔒 | | | no-multiple-empty-lines | Disallow multiple consecutive empty lines in Handlebars templates | ✅ 🔒 | 🔧 | | no-trailing-spaces | Disallow trailing whitespace at the end of lines | ✅ 🔒 | 🔧 |

Development

Prerequisites

  • Node.js 18+
  • npm

Setup

# Install dependencies
npm ci

# Run tests
npm test

# Run linting
npm run lint

CI/CD

This project uses Bitbucket Pipelines for continuous integration. The pipeline validates:

  • ✅ All tests pass (94 tests)
  • ✅ All linting passes (ESLint + documentation)
  • ✅ Code quality standards are met

The pipeline runs on:

  • Default branch: All commits
  • Pull requests: All PRs
  • Main branch: Manual deployment trigger

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Ensure tests and linting pass
  5. Submit a pull request

The CI pipeline will automatically validate your changes.