-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
There should be a way to ignore "repository" in package.json #28
Comments
Hmm, this plugin strongly expects the files you’re processing to be part of a GitHub/Bitbucket/GitLab repository. Much of the file/path resolving is based on that. Could you try passing in |
@NickHeiner Ping! |
Hi. Thanks for the follow-up. I was on vacation, so I didn't see this until now. I'm a little surprised that passing a repository is necessary, because:
I suspect that passing Is there no mode that just ignores links to the files on the remote web host? (e.g. |
* Use async file system operations * Check definitions, not references * Get repo info from Git instead of `package.json`, supporting non-npm projects * Support checking files on the API * Support non-hosted Git repos * Support self-hosted Git repos * Support case-insensitive hashes * Support streaming * Support multiple Git repos * Supports Gists * Add many more tests Closes GH-28. Closes GH-39. Closes GH-41.
I have the following field in my
package.json
:When I run
remark
, I get the following error:That error is repeated at location
1:1
of every one of my 158 markdown files in this repo. It's a bit misleading to suggest that the error is with the markdown itself, and not with the config passed in. There should only be one error displayed to the user, before any files are checked.But more pressingly, this issue blocks me from using this tool. I can't remove the
repository
field frompackage.json
, because other tools rely on it. But if I pass a falsey value for--use 'validate-links=repository:'
, the code reads from thepackage.json
anyway.I need a flag to say something like
--ignore-repository
. I'm happy to just forgo repository functionality and rely only on local checking.Thanks!
The text was updated successfully, but these errors were encountered: