Repository navigation
fix(solid-effect-atom): explicit peer ranges and build/test - #23
Merged
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit 69c370d
☁️ Nx Cloud last updated this comment at |
kattsushi
force-pushed
the
fix/solid-effect-atom-deps
branch
from
February 6, 2026 21:07
688f11d to
69c370d
Compare
kattsushi
added a commit
that referenced
this pull request
Mar 15, 2026
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.
Set explicit peerDependencies ranges for effect (^3.19.16) and solid-js (^1.9.11). Kept @effect-atom/atom as dependency via catalog. Verified build and tests succeed via Nx and Vitest.