Add devcontainer config

[hawkeyexl]

Description

Restore devcontainer functionality.

Type of contribution

• Quick change (typo, broken link, small wording change)
• Standard change (new content, examples, or improvements)
• Substantial change (new feature docs, major restructuring, tutorials)

Changes made

• Added devcontainer.json
• Updated Docusaurus bindings to work with forwarded ports
• Set up dependabot monitoring

Testing performed

• Previewed changes locally (npm run start)
• Tested all code examples
• Verified all links work
• Ran build successfully (npm run build)
• Ran style checks with Vale (if applicable)
• Added/updated Doc Detective tests (if applicable)

Checklist

• I have signed the Contributor License Agreement
• My changes follow the contribution guidelines
• I have used the appropriate content template (if applicable)
• All new content files use .mdx extension
• Front matter is included on all new pages
• Links use absolute paths (e.g., /docs/page not ../page)
• Code examples are complete and tested
• I have spell-checked my changes
• I have reviewed my own changes for errors

---

For reviewers:

• See Review Process for guidelines
• Focus on technical accuracy and user value
• Don't block on minor style issues—automation handles those

Summary by CodeRabbit

• Chores
  • Added a standardized development container for a consistent Node/TypeScript environment and useful developer tools.
  • Enabled automated weekly dependency updates via Dependabot.
  • Made the local development server reachable on all network interfaces for easier testing and remote access.

[coderabbitai]

Warning

Rate limit exceeded

@hawkeyexl has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 45 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 45eec85 and 9414438.

📒 Files selected for processing (1)

• .github/dependabot.yml (1 hunks)

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Adds a devcontainer for a Node.js + TypeScript environment, a Dependabot config to auto-update devcontainer dependencies weekly, and updates the npm "start" script to bind the Docusaurus dev server to 0.0.0.0.

Changes

Cohort / File(s)	Summary
Devcontainer config \.devcontainer/devcontainer.json	Adds a TypeScript Node.js devcontainer image, enables features (github-cli, jq-likes, vale, prettier, npm), forwards port 3000, and runs npm install in postCreateCommand. Several optional feature entries are commented out.
Dependabot configuration \.github/dependabot.yml	Adds Dependabot config (version: 2) to update the devcontainers ecosystem at the repo root on a weekly schedule.
Start script update package.json	Modifies the start script from docusaurus start to docusaurus start --host 0.0.0.0 to bind the server to all interfaces.

Sequence Diagram(s)

(omitted — changes are configuration-only and do not introduce new runtime control-flow between components)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Check devcontainer feature compatibility and any required feature configuration.
• Confirm Dependabot scope (devcontainers) and update cadence are intentional.
• Validate the --host 0.0.0.0 change for local and containerized development security/visibility.

Poem

🐰 In a box of code I quietly hop,
Tools and packages in tidy crop.
Dependabot hums a weekly tune,
Server opens wide beneath the moon—
Npm installs, and I go hop-hop! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add devcontainer config' directly corresponds to the primary change of adding a devcontainer.json file and related devcontainer setup, which is the main focus of this pull request.
Description check	✅ Passed	The description includes all key template sections with substantive content: clear purpose statement, appropriate contribution type selected, specific changes listed (devcontainer.json, Docusaurus bindings, dependabot setup), testing documented, and relevant checklist items completed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull Request Overview

This PR restores devcontainer functionality to the repository by adding configuration files to enable development in containerized environments. The key changes enable developers to use VS Code devcontainers with proper port forwarding and automated dependency installation.

• Added devcontainer configuration with Node.js 22 TypeScript base image and developer tools
• Modified Docusaurus start command to bind to all network interfaces for container port forwarding
• Set up automated dependency monitoring for devcontainer features via Dependabot

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
.devcontainer/devcontainer.json	Configures the devcontainer with Node.js 22, development tools (GitHub CLI, Vale, Prettier), port forwarding for Docusaurus (3000), and automatic npm install on container creation
.github/dependabot.yml	Enables automated weekly dependency updates for devcontainer features
package.json	Updates the start script to bind Docusaurus to 0.0.0.0 instead of localhost, allowing access to the dev server from outside the container

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/dependabot.yml (1)

7-12: Consider adding npm ecosystem monitoring for production dependencies.

The Dependabot config currently monitors only the devcontainers ecosystem. For a Node.js project, you typically want to also monitor npm (or npm_and_yarn) dependencies to catch security updates and new versions in package.json automatically.

If auto-updating npm dependencies is desired, apply this diff to extend the configuration:

 version: 2
 updates:
  - package-ecosystem: "devcontainers"
    directory: "/"
    schedule:
      interval: weekly
+
+ - package-ecosystem: "npm"
+   directory: "/"
+   schedule:
+     interval: weekly

If npm monitoring is intentionally deferred, this is fine as-is.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a52e23 and 3f6360d.

📒 Files selected for processing (3)

• .devcontainer/devcontainer.json (1 hunks)
• .github/dependabot.yml (1 hunks)
• package.json (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: CR
Repo: doc-detective/doc-detective.github.io PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-21T01:31:55.452Z
Learning: This is a Docusaurus v3 site for the Doc Detective docs; use the provided npm scripts for setup, dev, build, Storybook, and testing

📚 Learning: 2025-10-21T01:31:55.452Z

Learnt from: CR
Repo: doc-detective/doc-detective.github.io PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-21T01:31:55.452Z
Learning: This is a Docusaurus v3 site for the Doc Detective docs; use the provided npm scripts for setup, dev, build, Storybook, and testing

Applied to files:

• package.json

📚 Learning: 2025-10-21T01:31:55.452Z

Learnt from: CR
Repo: doc-detective/doc-detective.github.io PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-21T01:31:55.452Z
Learning: Applies to .scripts/buildSchemaReferencesV4.js : Use the prebuild script .scripts/buildSchemaReferencesV4.js (via npm run build-schemas) to process JSON schemas for docs

Applied to files:

• package.json

⏰ 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). (3)

• GitHub Check: Agent
• GitHub Check: Test deployment
• GitHub Check: runTests

🔇 Additional comments (3)

package.json (1)

7-7: The --host 0.0.0.0 flag is appropriate for devcontainer development.

Binding the dev server to all network interfaces enables access from the host machine, which is necessary for containerized development. This change correctly complements the port forwarding configuration in devcontainer.json (port 3000).

Note: The 0.0.0.0 binding does expose the dev server to the local network. This is standard for development but ensure this script is only used in development environments, not in production builds.

.devcontainer/devcontainer.json (2)

6-24: Well-configured devcontainer with appropriate features for the Doc Detective documentation project.

The image choice (official Microsoft typescript-node:1-22-bookworm) is solid, and the enabled features align well with the project's needs:

• vale is particularly relevant for documentation linting (aligns with Doc Detective's purpose)
• prettier supports code formatting within documentation
• github-cli and act enable local GitHub Actions testing
• jq-likes supports JSON utilities useful for schema validation

Verify that Node.js 22 is compatible with all project dependencies, particularly React 19.2.0, Docusaurus 3.9.2, and TypeScript 5.8.3. You can run npm ci or npm install within the devcontainer to confirm dependency compatibility.

---

28-31: Port forwarding and post-creation setup are correctly configured.

Port 3000 matches Docusaurus's default dev server port, and the postCreateCommand: "npm install" ensures dependencies are installed automatically when the container is created. This provides a smooth developer experience.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3f6360d and 45eec85.

📒 Files selected for processing (2)

• .devcontainer/devcontainer.json (1 hunks)
• .github/dependabot.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .devcontainer/devcontainer.json

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: CR
Repo: doc-detective/doc-detective.github.io PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-21T01:31:55.452Z
Learning: This is a Docusaurus v3 site for the Doc Detective docs; use the provided npm scripts for setup, dev, build, Storybook, and testing

Learnt from: CR
Repo: doc-detective/doc-detective.github.io PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-21T01:31:55.452Z
Learning: Applies to docusaurus.config.ts : Edit site configuration (navigation, plugins, sidebars, integrations) in docusaurus.config.ts

🪛 YAMLlint (1.37.1)

.github/dependabot.yml

[error] 10-10: syntax error: expected , but found ''

(syntax)

[hawkeyexl]

Merging despite test failure because of known bug.