fix(ci): flox upgrade to resolve nodejs package conflict - #43
Closed
garbas wants to merge 1 commit into
Closed
Conversation
The Lighthouse CI fails at 'flox activate' with: 'nodejs' conflicts with 'nodejs' — both packages provide include/node/common.gypi The explicit nodejs install and the nodejs bundled by clean-css-cli both resolved at priority 5 and collided, breaking the environment on main. Running 'flox upgrade' re-locks the environment and resolves the conflict, also bumping: google-lighthouse 12.8.2 -> 13.3.0 nodejs 22.21.1 -> 24.15.0 just 1.43.1 -> 1.51.0 imagemagick 7.1.2-8 -> 7.1.2-23 Verified locally: 'flox activate' now builds and node resolves to v24.15.0.
✅ Deploy Preview for planetnix ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
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
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.
Problem
The Lighthouse CI is failing for every PR (including #42) at the Activate Flox environment step:
The manifest installs
nodejsexplicitly andclean-css-cli(which bundles its ownnodejs). Both resolved at priority 5 and collide, so the environment fails to build. This is broken onmain, which means the CI's base-branch comparison step also fails — no PR can go green untilmainis fixed.Fix
Ran
flox upgrade, which re-locks the environment and resolves the conflict. It also bumps a few packages:Verification
Locally,
flox activatenow builds successfully andnode,lighthouse,justandcleancssall resolve (node v24.15.0, lighthouse 13.3.0).Only
.flox/env/manifest.{toml,lock}change — no site content touched.