fix: update package-lock.json to unblock CI and deploy#24
Merged
JesseRWeigel merged 1 commit intomainfrom Mar 16, 2026
Merged
Conversation
JesseRWeigel
had a problem deploying
to
github-pages
GitHub Actions
Failure
package-lock.json was missing lightningcss platform packages causing npm ci to fail in CI. Regenerate lock file and switch test workflow from npm ci to npm install for resilience. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
JesseRWeigel
force-pushed
the
fix/ci-lockfile
branch
from
c91c52e to
58a95c7
Compare
JesseRWeigel
had a problem deploying
to
github-pages
GitHub Actions
Failure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm citonpm installfor resilienceTest plan
🤖 Generated with Claude Code