Skip to content

chore(deps): remove unmaintained broken-link-checker dev dependency#221

Merged
kw-tmueller merged 1 commit into
masterfrom
chore/drop-broken-link-checker
Jun 23, 2026
Merged

chore(deps): remove unmaintained broken-link-checker dev dependency#221
kw-tmueller merged 1 commit into
masterfrom
chore/drop-broken-link-checker

Conversation

@DeepDiver1975

Copy link
Copy Markdown
Member

What

Removes the unmaintained broken-link-checker dev dependency and the npm run linkcheck script.

Why

broken-link-checker@^0.7.8 was last released around 2017 and is effectively unmaintained. It pulls in a large legacy transitive tree (deprecated nopter, urlobj, urlcache, uuid@2 which relies on Math.random, an old chalk/ansi stack) — a needless security and maintenance liability that keeps generating Dependabot noise.

It was only ever invoked through the linkcheck npm script and is not used in CI. Local link checking remains fully possible via the better-maintained tools already documented in the docs repository (Antora xref-validator, htmltest, filiph's linkcheck).

Changes

  • Drop the broken-link-checker devDependency
  • Drop the now-unused linkcheck npm script
  • Repoint agent/CLAUDE docs that referenced it to the documented alternatives (where present)
  • Regenerate package-lock.json (removes ~19 transitive packages)

No replacement dependency is added (per the repo policy of not introducing new dependencies without discussion).

Verification

  • npm install succeeds; the lockfile no longer contains any broken-link-checker family packages
  • npm run antora still builds the docs (a devDependency removal does not affect the build; verified end-to-end)
  • CI is unaffected (no workflow used linkcheck)

🤖 Generated with Claude Code

broken-link-checker@^0.7.8 is unmaintained (last released ~2017) and pulls in
a large legacy transitive tree (deprecated nopter, urlobj, urlcache, uuid@2
using Math.random, an old chalk/ansi stack), which is a needless security and
maintenance liability that drives Dependabot churn.

It was only exposed through the `npm run linkcheck` script and was never used
in CI. Local link checking is still possible via the better-maintained tools
documented in the docs repository (Antora xref-validator, htmltest,
filiph/linkcheck).

- drop the broken-link-checker devDependency
- drop the now-unused linkcheck npm script
- update agent/CLAUDE docs that referenced it to point at the documented tools
- regenerate package-lock.json (drops ~19 transitive packages)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>

@DeepDiver1975 DeepDiver1975 left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review by Claude Code review agent.

LGTM — clean removal of the unmaintained broken-link-checker dev dependency.

Verified:

  • package.json: broken-link-checker devDep and the linkcheck script both removed.
  • package-lock.json: the broken-link-checker node and transitive deps pruned. The diff also shows Git conflict markers (<<<<<<< / ======= / >>>>>>> from an earlier "remove dead Elasticsearch" change) being removed — those markers exist only in the base branch; the PR-head lockfile is conflict-marker-free and valid JSON, so this PR also tidies up that pre-existing breakage. Nice.
  • No dangling references — grepped package.json, lockfile, docs, and .github/workflows/ci.yml for linkcheck / broken-link-checker / blc: none remain.
  • CI: Build documentation and lint both green (confirms the resulting lockfile installs cleanly).
  • No CHANGELOG in this repo (n/a).

No blocking issues.

@kw-tmueller kw-tmueller merged commit 91a8fae into master Jun 23, 2026
2 checks passed
@kw-tmueller kw-tmueller deleted the chore/drop-broken-link-checker branch June 23, 2026 08:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants