-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
Tweak npm scripts #1197
base: master
Are you sure you want to change the base?
Tweak npm scripts #1197
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,11 +16,13 @@ | |
}, | ||
"homepage": "https://docs.pi-hole.net/", | ||
"scripts": { | ||
"build": "mkdocs build --clean", | ||
"build": "mkdocs build --clean --strict", | ||
"markdownlint": "markdownlint-cli2 \"**/*.md\" \"!**/node_modules/**\"", | ||
"linkinator": "npm run build && linkinator site --recurse --silent --skip \"^(?!http://localhost)\"", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is it still working when we remove the build step here? I'm asking because when we run There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, no. You need to build the docs manually. Alternatively, we could just change the CI script if you prefer that. |
||
"linkinator": "linkinator site --recurse --silent --skip \"^(?!http://localhost)\"", | ||
"pretest": "npm run build", | ||
"test": "npm run markdownlint && npm run linkinator", | ||
"serve": "mkdocs serve --dev-addr 0.0.0.0:8000" | ||
"serve": "mkdocs serve --dev-addr 0.0.0.0:8000", | ||
"start": "npm run serve" | ||
}, | ||
"devDependencies": { | ||
"linkinator": "^6.1.2", | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for the sake of documentation:
--strict
determines how warnings are handled. Set to halt processing when a warning is raised. Otherwise, print a warning and continue processing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took this from the CI config https://github.com/pi-hole/docs/blob/master/.github/workflows/ci.yml#L44