Nick Schonning

This isn't a pull request, see https://github.com/nzakas/parser-lib/issues/28 and https://github.com/nzakas/parser-lib/issues/97 for the discussion on why those PRs haven't been included.

@stubbornella you can manually rebase/merge the PR by following the intructions in the merge box. --- @arnogues I'm not sure what makes the most sense for the vendor prefixing. 1....

> I could add CSS Lint to the Bower repo myself, but it'd be a pain to have to download all those unnecessary files. You download all those files either...

PS: even from the bower main page suggests that isn't a good use case (emphasis theirs) > Bower is a package manager for the web. It offers a generic, unopinionated...

> OK fair enough, I should have reworded. For projects that check-in their bower dependencies, it's a pain to have to check in unnecessary files. They can check in the...

My 2 cents would be to see if you can create a repo like https://github.com/nodejs/remark-preset-lint-node based on the config. Then that config could be used by Node-core plus other repos

Probably not related, but the rewrite rules were updated recently https://github.com/nodejs/build/pull/2195

The remark-lint shouldn't be disabled on translations. It's already been catching things like broken reference links in translation PRs

Crowdin doesn't handle it though, and actually reformats the files so that they no longer follow the nodejs Markdown format styleguide

Ping @nodejs/nodejs-fr