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

@wayofdev/htmlhint-config

v4.0.0

Published

A shareable htmlhint configuration for projects.

Downloads

11

Readme

Shareable Htmlhint Config

📄 About

Package that contains shareable configurations for HTMLHint — a popular linting tool that helps to identify and fix problems in your HTML code.

→ Purpose

This package aims to provide a shared set of rules for HTMLHint to ensure consistent coding practices across a team or organization.

  • Provide a shared configuration that helps avoid inconsistencies and ensures that everyone follows the latest best practices and guidelines.
  • Make it easier for teams to use HTMLHint effectively and improve the quality of their HTML code.

💿 Installation

To use this configuration, you'll need to install the htmlhint and @wayofdev/htmlhint-config packages as devDependencies in your project. These packages should be installed in the package.json file of the specific app or package that needs them:

pnpm --filter=my-first-app add -D htmlhint @wayofdev/htmlhint-config

This package should be added to the root of your monorepo, where you have a file .htmlhintrc and a package.json file. Within your monorepo, you should have a structure with directories for your apps and packages, such as:

.
├── package.json (root)
├── apps
│   └── my-first-app
│       ├── package.json
│       └── ... (other app files)
└── packages
    └── my-first-package
        ├── package.json
        └── ... (other package files)

→ Configure

To configure the htmlhint, add script to package.json

pnpm pkg set scripts.lint:html="htmlhint --config ./node_modules/@wayofdev/htmlhint-config/index.json **/*.html"

💻 Usage

You can run the htmlhint command manually using the following pnpm command:

pnpm --filter=my-first-app lint:html

Alternatively, you can add it to lint-staged configuration to run together with Husky git hooks.

🤝 License

Licence

🧱 Credits and Useful Resources

Based on:

Related projects:

🙆🏼‍♂️ Author Information

This repository was created in 2023 by lotyp / wayofdev.

🙌 Want to Contribute?

Thank you for considering contributing to the wayofdev community! We are open to all kinds of contributions. If you want to:

  • 🤔 Suggest a feature
  • 🐛 Report an issue
  • 📖 Improve documentation
  • 👨‍💻 Contribute to the code

You are more than welcome. Before contributing, kindly check our guidelines.