I'd like to lint all strings in my JS assigned to the variable template or using the template tag html

eg:

const template = `
    <div class="foo">
        <span>this is a test</span>
    </div>
`;

or

function render(class_) {
    return = html`
        <div class="${class_}">
            <span>this is a test</span>
        </div>
    `;
}

I'm trying to get a project up and running but I need to disable some rules so they don't get triggered on CI run.

My config is:

{
    // names of npm modules to load into htmllint
    "plugins": [],

    // TODO: export htmllint's default cfg
    "options": [
      {"attr-name-style":"none"},
      {"attr-req-value":"none"}
    ]
}

But it doesn't seem to be being used. What is the correct way of using htmllint options in the rc file?

Allow the user to do file globbing, raw input strings, or pipe input into the htmllint command.

In my package.json i have:

    "htmllint": "0.8.0",
    "htmllint-cli": "0.0.7",
    "htmllint-loader": "2.1.4",

I get the following line:

local htmllint version is not supported: 0.8.0 != ^0.7.2

app.zip

Getting script to find all the html files is not doable with ** in path.

Map configuration values specified in the command line arguments to htmllint options.

Can i use this package wth vue files?

Hello,

I'd like to run htmllint on my project. However, running htmllint **/*.html gives a lot of false positives since it lints also the HTML files of the project dependencies stored in ./node_modules. The only workaround I can think of is to list all the directories (e.g. foo/**/*.html, bar/**/*.html) and the top-level HTML files (i.e. *.html). But with this approach, there is a big chance that I'll forget to add a newly created directories in the future and I won't notice that they are not linted.

It would be nice if there was a way to list directories/globs that should be excluded (like what you can do with .gitignore).

At the moment, the htmllint command assumes a local htmllint module will be available. The user might not be in a directory with the module, so it might be best to make sure a global htmllint module can be used.

May need to declare htmllint as a dependency too.

There should be some aria validation, as present within html5-lint.

per https://github.com/htmllint/htmllint/wiki/Options

Default: ['align', 'background', 'bgcolor', 'border', 'frameborder', 'longdesc', 'marginwidth', 'marginheight', 'scrolling', 'style', 'width']

The value of this option is a list of strings, each of which is an attribute name. Attributes with any of the given names are disallowed.

Isn't specifying height / width of an image best practice?

I just realized that there is no cross-platform way to use environment variables in NPM scripts. So, I guess that the only way to have a single source of file patterns is to store them in a file. Can you please consider adding a support to read the patterns from files? I would prefer a simple text file over e.g. a JSON file.

Add a CLI argument to output the current version.

I need this for the version check to work for https://github.com/necramirez/SublimeLinter-contrib-htmllint

Example:

$ htmllint --version
0.0.5

I vaguely remember that this worked before. I don't know why it doesn't work for me anymore -- it goes straight to execution (hence my ^C).

$ htmllint --version
local htmllint version is not supported: 0.4.0 != ^0.3.0
using builtin version of htmllint
^C

The --stdin flag that was added recently is a really important feature so it would be nice to have a new version released with it.

hello
I would like to be able to do

cat foo.html | htmllint

regards
thx

Hallo @mlochbaum / @nwoltman

was not fixed/merged in cli?
htmllint/htmllint#216

It has been over a year since the last version of htmllint-cli was released. There have been some important improvements since then (such as support for the latest version of htmllint) so it would be helpful to have these changes available on npm.

If I pass htmllint with a full path to an HTML file, like:
htmllint /Users/user/code/app_repo/apps/simple/src/app/app.component.html

htmllint-cli will say that file does not exist.

If that same file's path becomes relative: htmllint apps/simple/src/app/app.component.html, it will work properly.

@coalman I see that there is a commit that fixes this but a new build hasn't been pushed.

Add a man page. Should do this later, when the api is more stable.

Based on the TODO within lib/default_cfg.json, there's a need to include the default htmllint configuration values.

Currently, running htmllint init generates an empty file.

{
    // names of npm modules to load into htmllint
    "plugins": []

    // TODO: export htmllint's default cfg
}

From htmllint/htmllint#219

I'd like to use the none preset.

In other linting tools like eslint I only have console logging when at least one linting issue was found.
So I would like to have an option to disable "0 ouf of XYZ files" logging in htmllint-cli.

Like can be done with ESLint and Stylelint, as then we can append the htmllint results to it.

when there's no error, print nothing at all. print to stderr only on error.

Heya, this is just a friendly note to let you know that a new version of Liftoff and some of the dependencies commonly used in conjunction with it have been released. This release adds better support for situations where your user's configuration files are written using features behind a v8 flag (e.g. --harmony). Windows users and io.js users should see less issues if you upgrade!

Some helpful links:
https://github.com/tkellen/node-liftoff/blob/master/UPGRADING.md#100---200
https://github.com/tkellen/node-v8flags/blob/master/README.md#example
https://github.com/tkellen/node-hacker/blob/master/bin/hacker.js#L10-L14

Thanks!

Need to add some useful help info when the following is run:

$ htmllint --help
# or:
$ htmllint -h

The output at the moment is pretty boring. Allowing colored output (perhaps use the chalk module) would be really helpful.