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

htmlhint-config-nick2bad4u

v1.0.0

Published

Reusable HTMLHint policies for documents, accessibility, and fragments.

Readme

htmlhint-config-nick2bad4u

Continuous Integration

Reusable HTMLHint policies for complete documents, accessibility-focused checks, and HTML fragments.

Install

npm install --save-dev htmlhint htmlhint-config-nick2bad4u

Presets

| Preset | Intended use | | ----------------- | ---------------------------------------------------------- | | recommended | Balanced syntax, safety, document, and form checks. | | strict-document | Complete public documents with metadata and no inline CSS. | | accessibility | Structural accessibility requirements without style rules. | | fragment | Components/fragments that do not include an HTML shell. |

CLI usage

HTMLHint does not extend an installed package automatically, so provide the config path explicitly:

{
 "scripts": {
  "lint:html": "htmlhint --config node_modules/htmlhint-config-nick2bad4u/presets/recommended.json \"**/*.html\""
 }
}

The shorter compatibility path also selects recommended:

htmlhint --config node_modules/htmlhint-config-nick2bad4u/recommended.json index.html

JavaScript API

import {
 createHtmlHintConfig,
 getHtmlHintConfigPath,
 loadHtmlHintConfig,
} from "htmlhint-config-nick2bad4u";
import { HTMLHint } from "htmlhint";

const config = createHtmlHintConfig("strict-document", {
 "inline-style-disabled": false,
});
const messages = HTMLHint.verify(source, config);

const accessibilityPath = getHtmlHintConfigPath("accessibility");
const fragmentConfig = await loadHtmlHintConfig("fragment");

Consumer rule keys replace the selected preset values. HTMLHint rule configuration is flat, so no ambiguous deep-merge behavior is involved.

Choosing a preset

  • Use strict-document only for pages that own the full document shell.
  • Use fragment for partial templates and component fixture HTML.
  • accessibility is a useful additional gate, but HTMLHint is not a substitute for browser-based accessibility testing.

Requirements

  • Node.js ^22.22.3, ^24.16.0, or >=26.3.0
  • HTMLHint ^1.9.2

License

MIT