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

@saiballo/eleventy-plugin-validate-html

v1.0.4

Published

A plugin for 11ty which validates your site's pages after build.

Readme

eleventy-plugin-validate-html

A plugin, with options, that runs on the eleventy.after event and validates all the files that were built. Inspired by matt-auckland's plugin

MIT license

Installation

Available on npm:

npm install @saiballo/eleventy-plugin-validate-html --save

Add the plugin to your eleventy.config.js:

const pageValidation = require("@saiballo/eleventy-plugin-validate-html");

module.exports =  function(eleventyConfig) {
	eleventyConfig.addPlugin(pageValidation)
};

Usage

By default, the plugin checks all pages with the .html or .htm extensions. You can add or change extensions by providing a custom configuration. You can use "extensionList" parameter with a list of extensions (without the dot) separated by commas:

eleventyConfig.addPlugin(pageValidation, {
	"extensionList":  "ext1,ext2"
})

This plugin relies on html-validator. This allows you to use some configuration parameters from that package. The complete default configuration that you can override is:

eleventyConfig.addPlugin(pageValidation, {
	"extensionList":  "htm,html",
	"validator":  "WHATWG",
	"isLocal":  false,
	"isFragment":  false,
	"ignore": [],
	"whatwgConfig": {
		"elements": [],
		"rules": {}
	}
})

Parameters

// as previously seen, it is a comma-separated list of extensions to check for validation
"extensionList":  "htm,html"

// Possible values: "WHATWG" | "https://validator.w3.org/nu/"
//"WHATWG" is recommended. it will validate against the WHATWG standards.
"validator":  "WHATWG"

// set this to true if you want to validate local urls
"isLocal":  false

// set this to true only if all your pages are not a complete document
// if only certain pages are fragments, you can use "isFragment: true" in these pages as front matter data
"isFragment":  false

// only for "WHATWG" validator. string or array of strings or rules (when using WHATWG) you want the checker to remove in the response. even partial text.
// e.g. "ignore": ["Mismatched close-tag, expected '</div>' but found '</body>'", "another partial error response text"]
"ignore": [],

// only for "WHATWG" validator. additional configuration for elements and rules
"whatwgConfig": {
	"elements": [],
	"rules": {}
}

custom WHATWG configuration

// with this example, you add a custom tag called "customtag" to the valid tags in the validation. see https://html-validate.org/guide/metadata/simple-component.html
// additionally, you set the "heading-level" rule to "on" instead of "off". see https://html-validate.org/rules/index.html
"whatwgConfig": {
	"elements": [
		{
			"customtag": {
				"flow": true,
				"phrasing": true
			}
		}
	],
	"rules": {
		"heading-level": "error"
	}
}

Front Matter Data

Two parameters can be used as front matter data:

  • validateHtml: true|false to enable or disable validation for individual pages.
  • isFragment: true|false to declare a document as a fragment.

If the parameters are not set, the defaults are:

  • validateHtml: true
  • isFragment: false

Example:

---
validateHtml: true
isFragment: false
---

Team ARMADA 429

  • Lorenzo "Saibal" Forti

License