Skip to content

chore(hooks): install site deps with npm ci in session start - #57

Merged
Anton-Babaskin merged 1 commit into
mainfrom
claude/website-seo-scqzs2
Sep 30, 2026
Merged

Anton-Babaskin merged 1 commit into
mainfrom
claude/website-seo-scqzs2

Conversation

@Anton-Babaskin

Copy link
Copy Markdown
Owner

What changed?

The SessionStart hook in .claude/hooks/session-start.sh ran npm install in web/. The npm in the remote container drops the libc fields from web/package-lock.json, so every cloud session started with a modified lockfile. The hook now runs npm ci, which installs exactly what the lockfile says and never writes to it.

Verification

  • bash -n passes.
  • I ran the hook with CLAUDE_CODE_REMOTE=true: it installed 33 packages, imported the proxy CA, and left git status clean afterwards.

Risk and rollout

  • The hook only runs in remote Claude Code sessions. It doesn't affect CI, the site build or local machines.

Checklist

  • No backend or site files touched
  • No credentials committed

🤖 Generated with Claude Code

https://claude.ai/code/session_01FXf3z2i7xUTUkkt54jb3UP


Generated by Claude Code

npm install in the remote session rewrote web/package-lock.json (the
container's npm drops the libc fields), leaving every session with a
dirty tree. npm ci installs exactly the lockfile and never writes it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FXf3z2i7xUTUkkt54jb3UP
@Anton-Babaskin
Anton-Babaskin merged commit 498cfcb into main Sep 30, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants