Follow-up to #79, which was merged before this commit landed.
Summary
Bump @effect-view/vite-plugin from 0.0.2 to 0.2.0 to match effect-view@0.2.0
Fix the plugin's peer range: effect-view@^0.1.0 → ^0.2.0
For 0.x versions a caret range is patch-only within the minor, so ^0.1.0 (= >=0.1.0 <0.2.0) excludes 0.2.0 and would have caused a peer-dependency mismatch.
Verification
bun run lint:tsc✅ (9/9 tasks)
bun install clean, no peer warnings
Follow-up to #79, which was merged before this commit landed.
## Summary
- Bump `@effect-view/vite-plugin` from `0.0.2` to `0.2.0` to match `effect-view@0.2.0`
- Fix the plugin's peer range: `effect-view@^0.1.0` → `^0.2.0`
For `0.x` versions a caret range is patch-only within the minor, so `^0.1.0` (= `>=0.1.0 <0.2.0`) excludes `0.2.0` and would have caused a peer-dependency mismatch.
## Verification
- `bun run lint:tsc` ✅ (9/9 tasks)
- `bun install` clean, no peer warnings
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #79, which was merged before this commit landed.
Summary
@effect-view/vite-pluginfrom0.0.2to0.2.0to matcheffect-view@0.2.0effect-view@^0.1.0→^0.2.0For
0.xversions a caret range is patch-only within the minor, so^0.1.0(=>=0.1.0 <0.2.0) excludes0.2.0and would have caused a peer-dependency mismatch.Verification
bun run lint:tsc✅ (9/9 tasks)bun installclean, no peer warningsPull request closed