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

html-w3c-validator

v1.7.0

Published

CLI for validating HTML pages using validator.w3.org.

Downloads

214

Readme

📜 About

html-w3c-validator is a CLI tool to validate HTML pages using validator.w3.org.

You might use a JavaScript framework or simply use HTML but you should always validate your production HTML and this validation should be part of your CI/CD pipeline (tests, linting, etc.).

Why is HTML page validation important?

Quote from https://validator.w3.org/docs/help.html#why-validate:

One of the important maxims of computer programming is: "Be conservative in what you produce; be liberal in what you accept."

Browsers follow the second half of this maxim by accepting Web pages and trying to display them even if they're not legal HTML. Usually this means that the browser will try to make educated guesses about what you probably meant. The problem is that different browsers (or even different versions of the same browser) will make different guesses about the same illegal construct; worse, if your HTML is really pathological, the browser could get hopelessly confused and produce a mangled mess, or even crash.

⚙️ Getting Started

You can combine html-w3c-validator with start-server-and-test to validate HTML pages of your project.

Prerequisites

Node.js >= 16.0.0

Installation (with start-server-and-test)

npm install --save-dev html-w3c-validator start-server-and-test

⚙️ Configuration

package.json

{
  "scripts": {
    // Command to start the server serving your HTML pages (e.g: using vercel/serve)
    "start": "serve \"./build\"",

    // Command to validate your HTML pages
    "test:html-w3c-validator": "start-server-and-test \"start\" \"http://127.0.0.1:3000\" \"html-w3c-validator\"",
  },
}

.html-w3c-validatorrc.json

{
  "$schema": "./node_modules/html-w3c-validator/schema/schema.json",

  // URLs to validate.
  "urls": ["http://127.0.0.1:3000/", "http://127.0.0.1:3000/about"],

  // Files to validate.
  "files": ["./index.html", "./about.html"],

  // Specify the severities of the validator messages to report. (default: ["warning", "error"])
  "severities": ["info", "warning", "error"],
}

Usage

node --run test:html-w3c-validator

Example of output (in case of success):

✔ Validating http://127.0.0.1:3000/
✔ Validating http://127.0.0.1:3000/about

Success: HTML validation (W3C) passed! 🎉

See the ./example folder for practical usage.

Options

--current-working-directory <path>  The current working directory (default: `process.cwd()`).
-V, --version                       Output the version number.
-h, --help                          Display help for command.

💡 Contributing

Anyone can help to improve the project, submit a Feature Request, a bug report or even correct a simple spelling mistake.

The steps to contribute can be found in the CONTRIBUTING.md file.

📄 License

MIT