Skip to content
πŸ’‘ A hinting engine for the web
TypeScript JavaScript CSS HTML
Branch: master
Clone or download

Latest commit

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.dependabot Chore: Update proxyquire and fix tests Oct 17, 2019
.github Docs: Update CONTRIBUTING.md with new CoC Nov 1, 2019
.vscode Build: Add `testMode` to release Nov 18, 2019
@types Chore: Enable strict type-checking Oct 9, 2018
azure-pipelines Chore: Always use latest VM images for CI Jan 28, 2020
packages Upgrade: Bump @types/semver from 7.1.0 to 7.2.0 Jun 13, 2020
release Chore: Add --skipVsce to release script to allow skipping vscode publish May 18, 2020
scripts Upgrade: Bump @types/jsdom from 12.2.4 to 16.2.0 Apr 20, 2020
.editorconfig Build: Disable `Travis CI` Jan 18, 2019
.eslintignore Fix: Prune UserConfig data Aug 2, 2019
.eslintrc.json Chore: Refactor ESLint commands Dec 6, 2019
.gitattributes Chore: Avoid normalizing binary files Feb 7, 2019
.gitignore New: Make CLI, hints, and formatters localizable Jul 18, 2019
.markdownlintrc Build: Disable unnecessary markdownlint rule Oct 7, 2019
.npmrc Build: Avoid possible warnings when using `nvm` Apr 12, 2019
.nycrc Build: Fix code coverage report May 7, 2019
LICENSE.txt Update copyright to standard JSF statement Jun 20, 2017
README.md Docs: Charter and Governance Mar 5, 2020
azure-pipelines.yml Build: Tweak Azure Pipelines configuration Jan 15, 2019
package.json Upgrade: Bump @types/semver from 7.1.0 to 7.2.0 Jun 13, 2020
tsconfig.json New: Utility to run webhint in a web worker Apr 7, 2020
yarn.lock Upgrade: Bump @types/semver from 7.1.0 to 7.2.0 Jun 13, 2020

README.md

webhint

Build Status Gitter FOSSA Status

Quick start user guide

webhint is a customizable linting tool that helps you improve your site's accessibility, speed, cross-browser compatibility, and more by checking your code for best practices and common errors.

It can be run from the command line (CLI), via a browser extension, as a VS Code extension, and from the online service.

To use it from the from the CLI you will need to install Node.js (v10.x or later) on your machine, and you can use npx to test it.

Testing with npx

Run the following command:

npx hint https://example.com

This will analyze https://example.com using the default configuration.

Installing webhint locally

Install webhint as a devDependency of your project:

npm install hint --save-dev

And then add a script task to your package.json:

{
    ...
    "scripts": {
        "webhint": "hint"
    }
}

And run it via:

npm run webhint -- http://localhost:8080

Or if you are using yarn you can skip the step to create a task and run directly:

yarn hint http://localhost:8080

To know more about webhint, how to configure it, etc. see the online user guide, or the local version for the most recent content.

Contributing to webhint

This project follows a monorepo pattern. That means that the code for all the webhint flavors (CLI, browser and VS Code extension, hints, formatters, etc.) are in here and are published as separate npm packages.

To build the project from the source you will need to install a recent version of node and yarn. Once you've done this run the following from the root of your cloned version:

yarn
yarn build

This can take a bit so please be patient.

To learn more about the internals of webhint, the structure of the project, how to create new hints, parsers, formatters, etc, take a look at the online contributor guide (or the local version).

Contributing to the browser and VS Code extensions

To learn about how to build one of the extensions please check the CONTRIBUTING.md files for each of these packages:

Code of Conduct

All projects in the webhintio organization follow this CoC which adheres to the OpenJS Foundation Code of Conduct.

Other important links

License

The code is available under the Apache 2.0 license.

FOSSA Status

You can’t perform that action at this time.