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 🙏

© 2024 – Pkg Stats / Ryan Hefner

htmlhint-plugin-blocked-words

v1.0.2

Published

An [HTMLHint](https://htmlhint.com/) plugin that allows users to block arbitrary phrases in HTML code.

Downloads

33,724

Readme

htmlhint-plugin-blocked-words

An HTMLHint plugin that allows users to block arbitrary phrases in HTML code.

Installation

You probably want this as a dev dependency:

npm i -D htmlhint-plugin-blocked-words

Load into HTMLHint

CLI

If calling HTMLHint via its CLI, you'll need to use the --rulesdir or -r option for HTMLHint:

npx htmlhint index.html -r node_modules/htmlhint-plugin-blocked-words/dist/rules

JS API

If calling HTMLHint via its JS API (shown below as HTMLHint.verify), you can use the addAllRules export from this package:

import {readFileSync} from 'fs';
import {HTMLHint} from 'htmlhint';
import {addAllRules} from 'htmlhint-plugin-blocked-words';

// this must be added before your HTMLHint api calls. It only needs to be called once per process.
addAllRules();

const yourCode = readFileSync('filename.ts').toString();
HTMLHint.verify(yourCode);

Temporarily ignoring

Add the following comment to the top of a file to turn off a rule for that file. (Note that HTMLHint does not document this anywhere but it works.)

<!-- htmlhint block-words:false -->
<html>
    <head>
        <title>Document Title</title>
    </head>
    <body>
        Stuff
    </body>
</html>

Rules

block-words

This is the main (currently only) rule, used to block phrases in tag names, text, attribute names, or attribute values.

This rule accepts an object with the following type:

export type BlockWordsOptions = {
    all?: string[];
    attributeNames?: string[];
    attributeValues?: string[];
    tagNames?: string[];
    text?: string[];
};

Each string in each array is treated as a regular expression, so RegExp syntax can be used. (Make sure to escape the backslash though, like this: "\\s".)

  • all: checks each HTML node's entire raw text.
  • attributeNames: checks every attribute name (such as class, id, or custom attributes).
  • attributeValues: checks every attribute's values (such as this is a list of class names in <div class="this is a list of class names"></div>).
  • tagNames: checks every tag name (such as div).
  • text: checks the text of each node (such as this is some text in <div>this is some text</div>).

Turn off the rule by giving it a falsy value, such as false, null, or even an empty string ''.

Example usage:

{
    "block-words": {
        "attributeValues": ["\\bbad-phrase\\b"]
    }
}

With that given htmlhintrc file, the following is invalid:

<div class="bad-phrase"></div>

While the following is valid:

<div>bad-phrase</div>

(To block bad-phrase also in text, use the all or text property in the block-words options.)