Skip to content

fix(update): use npm ci to prevent stale node_modules after update#960

Open
ceotjoe wants to merge 1 commit intoaccius:Stagingfrom
ceotjoe:fix/update-use-npm-ci-v2
Open

fix(update): use npm ci to prevent stale node_modules after update#960
ceotjoe wants to merge 1 commit intoaccius:Stagingfrom
ceotjoe:fix/update-use-npm-ci-v2

Conversation

@ceotjoe
Copy link
Copy Markdown
Collaborator

@ceotjoe ceotjoe commented May 7, 2026

Summary

  • Replaces npm install --include=dev with npm ci in scripts/update.sh
  • npm ci wipes node_modules before installing, so newly added production dependencies (like rss-parser in v26.3.x) are guaranteed to be present after an update
  • Fixes a user-reported issue where updating via update.sh left rss-parser absent, causing [FATAL] Cannot find module 'rss-parser' on service restart; re-running setup-pi.sh (which writes into a clean tree) resolved it

Test plan

  • Run update.sh on a Pi with an existing install from before rss-parser was added and confirm the service starts cleanly
  • Confirm npm ci fails fast if package.json and package-lock.json are out of sync (expected safety net behaviour)

🤖 Generated with Claude Code

…modules

npm ci deletes node_modules and reinstalls from the lockfile exactly,
so newly added production dependencies (e.g. rss-parser in v26.3.x)
are guaranteed to be present after an update rather than silently
absent from an existing, incremental node_modules tree.

Fixes: Cannot find module 'rss-parser' after running update.sh

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.

[BUG] Service fails to start after 26.3.1 update

1 participant