chore: remove npm dependencies, using only bun for docs generation

[wakeful]

Description

chore: remove npm dependencies, using only bun for docs generation

TODOs

Read the Gruntwork contribution guidelines.

• I authored this code entirely myself
• I am submitting code based on open source software (e.g. MIT, MPL-2.0, Apache)]
• I am adding or upgrading a dependency or adapted code and confirm it has a compatible open source license
• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

chore: remove npm dependencies, using only bun for docs generation

Migration Guide

n/a

Summary by CodeRabbit

• Chores
  • Removed Dockerfile and Docker Compose configuration for the docs-starlight service. Docker-based development and deployment are no longer supported for this service.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
terragrunt-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 11, 2025 2:56pm

[coderabbitai]

📝 Walkthrough

Walkthrough

This change removes the Dockerfile and Docker Compose configuration for the docs-starlight service. The deleted files previously defined the build and development environment for the service using Docker, including dependency installation, custom patching, and live-reload setup.

Changes

File(s)	Change Summary
docs-starlight/Dockerfile	Removed the Dockerfile defining the multi-stage build for the service.
docs-starlight/docker-compose.yml	Removed the Docker Compose configuration for local development.

Possibly related PRs

• fix: Adjusting Dockerfile for Starlight docs #4496: Modifies and fixes the Dockerfile for docs-starlight, directly related as both PRs involve handling of the same Dockerfile.

Suggested reviewers

• yhakbar

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b7c73be and 321d72e.

⛔ Files ignored due to path filters (1)

• docs-starlight/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• docs-starlight/Dockerfile (0 hunks)
• docs-starlight/docker-compose.yml (0 hunks)

💤 Files with no reviewable changes (2)

• docs-starlight/docker-compose.yml
• docs-starlight/Dockerfile

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Pull Request has non-contributor approval
• GitHub Check: Build (darwin/arm64)
• GitHub Check: Run pre-commit hooks
• GitHub Check: lint

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.