Skip to content

Fix codespace boot failure by using updateContentCommand for npm ci #208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Copilot wants to merge 3 commits into
base: main
Choose a base branch
from
+13 −2
Draft

Fix codespace boot failure by using updateContentCommand for npm ci #208

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cb6f004
Initial plan
Copilot Feb 11, 2026
d243ca8
Fix codespace boot failure by using updateContentCommand instead of p…
Copilot Feb 11, 2026
dab2dfa
Document devcontainer fix in CONTRIBUTING.md
Copilot Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .devcontainer/devcontainer.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,6 @@
}
}
},
"postCreateCommand": "npm ci",
"updateContentCommand": "npm ci",
"remoteUser": "node"
}
13 changes: 12 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ Thank you for your interest in contributing to the Copilot Token Tracker extensi
- [Development Environment Setup](#development-environment-setup)
- [Using the DevContainer (Recommended)](#using-the-devcontainer-recommended)
- [Why Use a DevContainer for AI-Assisted Development?](#why-use-a-devcontainer-for-ai-assisted-development)
- [DevContainer Configuration Notes](#devcontainer-configuration-notes)
- [Manual Local Setup](#manual-local-setup)
- [Development Workflow](#development-workflow)
- [Available Scripts](#available-scripts)
Expand Down Expand Up @@ -114,7 +115,7 @@ The devcontainer allows you to confidently let AI assistants:
- **Zero Configuration:** AI can start working immediately without environment setup
- **Pre-installed Tools:** All required dependencies are ready to go
- **Known State:** AI agents can make more accurate suggestions knowing the exact environment
- **Automatic Setup:** The `postCreateCommand` ensures dependencies are always up-to-date
- **Automatic Setup:** The `updateContentCommand` ensures dependencies are installed after content updates

### 💡 Real-World Scenario

Expand All @@ -133,6 +134,16 @@ Without a devcontainer, you'd need to:
- Risk system-level changes
- Potentially need to uninstall packages or revert changes

### DevContainer Configuration Notes

The `.devcontainer/devcontainer.json` uses `updateContentCommand` instead of `postCreateCommand` for dependency installation:

- **Why `updateContentCommand`?** This lifecycle hook runs after workspace content is updated (including initial clone), making it more reliable for dependency installation in GitHub Codespaces and similar environments.
- **Benefits:** More reliable timing, better suited for `npm ci` operations, and follows devcontainer best practices.
- **Lifecycle Order:** The devcontainer executes hooks in this order: `onCreateCommand` → `updateContentCommand` → `postCreateCommand` → `postStartCommand`.

Using `updateContentCommand` prevents timeout issues that can occur with `postCreateCommand` during initial codespace creation, especially for projects with many dependencies.

## Manual Local Setup

If you prefer not to use the devcontainer, you can set up the extension locally:
Expand Down