-
-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: --cache similar to ESLint for remark-cli? #338
Comments
I will give this a shot this weekend :) |
Turns out I'm completely packed till I leave for vacation in two weeks so I won't be able to do this for at least a month. To not claim a stale contribution, consider me out until I say here otherwise. So if anyone is excited to pick this up you don't have to hesitate :) |
Subject of the issue
It would be useful for Node.js core if remark-cli had a --cache option similar to that used in ESLint. We fake it right now in our Makefile by generating a timestamp file and only linting if the directory of markdown files was modified after the timestamp file. This works OK in most situations but has the following disadvantages:
Your environment
remark-cli
,remark-preset-lint-node
node
10.4.1,npm
6.1.0Steps to reproduce
We use something like
remark-cli/cli.js -q -f doc
wheredoc
is a directory with a lot of markdown files. Ideally, it would be great if we could pass--cache
to generate a.remarklintcache
file the way ESLint generates an.eslintcache
file.Expected behaviour
With the cache file, running the command again and again should be much faster (unless all the files change, a rule is changed, or the version of
remark-cli
is updated).Actual behaviour
Well, the feature isn't implemented so I get the
remark-cli
help message.The text was updated successfully, but these errors were encountered: