Skip to content

chore: remove unused npm dependencies#641

Open
mesutoezdil wants to merge 4 commits into
Project-HAMi:masterfrom
mesutoezdil:chore/remove-unused-deps
Open

chore: remove unused npm dependencies#641
mesutoezdil wants to merge 4 commits into
Project-HAMi:masterfrom
mesutoezdil:chore/remove-unused-deps

Conversation

@mesutoezdil

@mesutoezdil mesutoezdil commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Note

This PR is stacked on #556 and #630, so until those merge, the "Files changed" diff against master also shows their lockfile refresh and overrides block. The only change introduced by this PR itself is the removal of three dependencies; see the last commit for the isolated diff. Merge order: #556 -> #630 -> this, each becoming a trivial diff as its parent lands.

What

Removes three dependencies that nothing in the repo uses:

  • asciinema-player (dependency): no import, no CSS reference, no MDX usage anywhere in src, themes, docs, tutorials, blog or i18n
  • react-github-btn (dependency): the star button is a custom component (src/components/gitHubButton.js) built on Font Awesome
  • gh-pages (devDependency): deployment moved to Netlify (netlify.toml); the docusaurus deploy script does not use this package

Why

Every installed package is attack surface for the next supply-chain advisory and noise in npm audit. These three contribute nothing to the build.

Testing

  • npm run build:fast passes after removal
  • npm audit still reports 0 vulnerabilities

Part of #628

Refreshed against latest master to cover advisories published
through Jul 21. Resolves 20 of 47 npm audit findings including
both critical ones. Remaining findings need breaking upgrades
in the Docusaurus toolchain.

Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
Copilot AI review requested due to automatic review settings July 22, 2026 13:19
@hami-robot
hami-robot Bot requested review from wawa0210 and windsonsea July 22, 2026 13:19
@hami-robot

hami-robot Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mesutoezdil
Once this PR has been reviewed and has the lgtm label, please assign archlitchi for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@netlify

netlify Bot commented Jul 22, 2026

Copy link
Copy Markdown

Deploy Preview for project-hami ready!

Name Link
🔨 Latest commit 7c0b0a9
🔍 Latest deploy log https://app.netlify.com/projects/project-hami/deploys/6a63990b0b56c00008e9b880
😎 Deploy Preview https://deploy-preview-641--project-hami.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@mesutoezdil, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 73a333da-34d6-47e4-a9b7-17dd96fb62bc

📥 Commits

Reviewing files that changed from the base of the PR and between bf4e9cf and 7c0b0a9.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the website’s npm dependency set, primarily aiming to remove unused packages from the Docusaurus-based documentation site.

Changes:

  • Remove unused dependencies: asciinema-player, react-github-btn, and devDependency gh-pages.
  • Add npm overrides pins for several transitive dependencies (security/compatibility-related).
  • Regenerate package-lock.json, resulting in broader transitive dependency updates.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File Description
package.json Removes the three declared unused packages and adds an overrides section for pinned transitive deps.
package-lock.json Removes the deleted packages from the lockfile and updates a large portion of the resolved dependency tree accordingly.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread package.json Outdated

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

Comment thread package.json
Add npm overrides scoped to the parents that need them, pinned to
exact versions: js-yaml, markdown-it and run-con under
markdownlint-cli, serialize-javascript under copy-webpack-plugin
and css-minimizer-webpack-plugin, and uuid under sockjs. Scoping
keeps unrelated subtrees on their own versions. markdownlint-cli
stays at 0.48.0 and run-con at 1.3.2 because their newer releases
pull deps requiring Node 22 while CI runs Node 20. npm audit now
reports 0 vulnerabilities.

Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
asciinema-player and react-github-btn are not imported anywhere in
the site code. gh-pages is unused since deployment moved to Netlify.
Fewer dependencies means a smaller vulnerability surface.

Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
Copilot AI review requested due to automatic review settings July 22, 2026 14:00
@mesutoezdil
mesutoezdil force-pushed the chore/remove-unused-deps branch from 8c57ed8 to 8fcad15 Compare July 22, 2026 14:00

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.

@mesutoezdil
mesutoezdil requested a review from rootsongjc July 23, 2026 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants