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

w3c-quicky

v0.6.1

Published

Tool for validating files according to W3C rules

Downloads

1

Readme

w3c-quicky

Check your code according to w3c rules in fast and efficient way 🔥

How to use it?

  1. Install it using npm i -DE w3c-quicky.

  2. Now you can execute it through npx like this npx w3c-quicky \"./path/to/dir/**/*.html\".

    You don't need to wrap your glob pattern in "" but it's recommended. Many shells are automatically resolving globs in not the most optimal way.

  3. If you need help check out other options npx w3c-quicky --help

Config file

Config file will help you have more control over validated files. File is optional, but if you decided to use it has to be placed in your project root directory and be named as .w3cquicky.json.

Content of the file has structe like below.

{
  "excludedPaths": [],
  "ignoredRules": []
}
  • excludedPaths is an string[] whcih takes static paths or glob patterns. Paths matching this option will be excluded from validation
  • ignoredRules is also an string[] which takes validation messages or parts of it and return validation results with ommited rules.

Example:

{
  "excludedPaths": ["**/some-specific-file.html", "**/*/*test*.html"],
  "ignoredRules": [
    "Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.",
    "Cache-Control"
  ]
}

Excluding paths or ignoring rules is not possible through command line at the moment for lower readability reasons.

Troubleshooting

  • Validation failed: Too many requests. Please wait a bit before trying again.

    Unfortunately, validation server has limits and if you try to check too many files in short period of time it will return 429 status code. If you can, please try to limit included files to check or do it less frequently.

For developers

How to work with code?

  • Install dependencies via npm i
  • Start building process with watcher npm start
  • Run script via node ./dist/bin/index.js <sources> or use Run and Debug tool in VSCode

TODO:

  • Add tests
  • Add benchmarks
  • Validate response body
  • Setup github actions
  • Add checksums and cache results?