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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@firefoxic/bemlint

v6.0.0

Published

CLI tool for linting HTML using BEM methodology.

Readme

bemlint

License: MIT Changelog NPM version Test Status

This CLI tool validates your HTML markup against BEM methodology.

Check MIGRATION_GUIDE.md if upgrading from gulp-html-bemlinter.

Installation

Globally

pnpm add -g @firefoxic/bemlint

Locally

pnpm add -D @firefoxic/bemlint

Usage

bemlint is invoked via the command line:

  • with globally installation:

    bemlint <inputs>
  • with locally installation (in a project):

    pnpm exec bemlint <inputs>
  • without installation:

    pnpm dlx @firefoxic/bemlint <inputs>

For brevity, the examples below will use the global installation variant. Expand each of them for your specific case.

Linting variants

  • Lint a single file

    bemlint dist/index.html
  • Lint multiple files with glob patterns

    bemlint src/**/*.html
  • Lint all HTML files in a directory

    bemlint dist/blog
  • Specify multiple inputs

    bemlint dist/about.html dest/blog

Understanding results

✅ No issues found

$ bemlint valid.html
# No output, silently exit with code 0
$ echo $? # or $status in fish
0

❌ BEM issues found

$ bemlint dest/problematic.html

HTML
└─ BODY
   └─ DIV.card
      ├─ H1.card__title
      └─ DIV.other__element ❌ Element outside its block!

File: dest/problematic.html
bemlint: 1 issue found!

$ echo $?
1

What gets checked

Currently, bemlint only supports “two-dashes” BEM notation:

  • ✅ Proper BEM naming — .block-name__elem-name--mod-name_mod-value

The following are considered errors:

  • ❌ Elements outside their blocks — .block__elem:not(.block *)
  • ❌ Elements mixed with their blocks — .block.block__element
  • ❌ Elements of elements — .block__elem__sub-elem
  • ❌ Modifiers without base entity — .block--mod-name:not(.block)
  • ❌ Wrong element separators — block-name_elem-name
  • ❌ Wrong modifier value separators — block--mod-name__mod-value

Common use cases

In package.json scripts (with installation as a dependency)

{
	"scripts": {
		"build": "...",
		"prelint:bem": "node --run build",
		"lint:bem": "bemlint \"dist/**/*.html\""
	}
}

In CI/CD (without installation as a dependency)

- name: Check BEM compliance
  run: pnpm dlx @firefoxic/bemlint "dist/**/*.html"

Happy BEM linting! 🎉