Small software for browser and application problems that should not need to be solved from scratch.
10 projects · 4 areas · independently installable
Focused React inspection and interaction primitives with explicit gesture, accessibility and ownership boundaries.
Inspect the object you actually have.
A React inspector for real JavaScript object graphs. Explore values, follow shared references and cycles, and keep your application in control.
Accessible bottom sheets for React with snap points, gesture and scroll coordination, focus management and interruption-safe motion.
Composable swipe-reveal actions for React rows with measured action regions, logical RTL sides, keyboard interaction and optional full swipe.
Keep floating React content aligned with an anchor through portals, scrolling, resizing and layout changes — without owning popup semantics.
Pull-to-refresh mechanics with scroll ownership, resistance, threshold hysteresis and an application-owned asynchronous refresh lifecycle.
Drag-to-dismiss mechanics for arbitrary React content with intent detection, velocity, resistance and settling — while the application owns removal.
Small abstractions around browser behavior and geometry that application code otherwise has to rebuild.
Reliable viewport coordinates for carets in inputs, textareas and editable DOM, with observation and virtual references for floating UI.
Shared reactive visual-viewport, zoom, keyboard-occlusion and safe-area geometry for React logic when CSS or a one-off browser API read is not enough.
Framework-independent JavaScript primitives for application semantics.
Deeply readonly, lazy, live views over owner-controlled mutable JavaScript data.
Conservative developer tools for migration, analysis and source transformation.
Review-first Angular template migration tooling for removing Flex Layout with compiler-aware analysis, explicit targets and diagnostics for cases that should remain manual.
Alpha — API and behavior may change. Beta — API settling, broader validation. Stable — compatibility expectations established.
No shared runtime. No required NIPE stack. Each project owns its API, documentation and release cycle.
Caret Geometry can provide a virtual caret reference to a compatible positioner. The positioner owns placement. Composition starts with matching boundaries, not installing the whole catalogue.
Each project solves one problem and stops before it becomes a framework. Application state stays with the application.
Interaction and geometry projects document browser behavior, automated tests and the limits of physical-device verification.
Strict TypeScript APIs, explicit ownership and inspectable output. The codemod leaves uncertain cases unchanged and reports why.