Update devcontainer.json with Vercel features

[Jonathancombs782]

Added Vercel features and Corepack to the devcontainer.

Summary by Sourcery

Add a development container configuration to support a standardized dev environment with additional tooling.

Build:

• Introduce a .devcontainer/devcontainer.json configuration to define the development container setup, including Vercel-related tooling and Corepack support.

Chores:

• Set up repository-level devcontainer metadata to improve developer onboarding and environment consistency.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bitcoin	Ready	Preview, Comment	Feb 17, 2026 5:56am

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Introduces a new devcontainer configuration that adds Vercel-related tooling and Corepack support to the development container environment.

File-Level Changes

Change	Details	Files
Add a devcontainer configuration to support Vercel tooling and Corepack inside the development container.	Create a new .devcontainer/devcontainer.json file to define the development container setup. Configure the container with Vercel-related features (e.g., CLI/tools) for deployment and preview workflows. Enable or configure Corepack in the container so Node package managers (e.g., pnpm, yarn) are managed consistently across environments.	.devcontainer/devcontainer.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider whether adding Vercel-specific features directly into the shared devcontainer is appropriate for all contributors; if this is primarily for a subset of workflows, it might be better isolated into a separate devcontainer config or made opt-in via features instead of being the default.
• If Corepack/Node are being enabled inside the devcontainer, ensure the Node.js version (and any package manager versions) are explicitly pinned to keep the development environment reproducible across machines and over time.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider whether adding Vercel-specific features directly into the shared devcontainer is appropriate for all contributors; if this is primarily for a subset of workflows, it might be better isolated into a separate devcontainer config or made opt-in via features instead of being the default.
- If Corepack/Node are being enabled inside the devcontainer, ensure the Node.js version (and any package manager versions) are explicitly pinned to keep the development environment reproducible across machines and over time.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}