React / Next.js
Components, dashboards, landing pages and full App Router starters. TypeScript, Tailwind and the parts of a Next.js build that take longest to get right.
Every package here was unpacked and its source analysed for malware, prompt-injection payloads, build failures and copied work before it could be listed.
Glassmorphic UI Kit — Accessible React 19 Components for Tailwind CSS v4
Twelve glassmorphic React components (card, panel, button, input, select, modal, tabs, toast, navbar, badge, tooltip, skeleton) built on a CSS-first Tailwind v4 @theme token layer, with generated .d.ts and zero runtime dependencies. Keyboard behaviour is implemented and executed rather than approximated: 66 Vitest tests plus a headless-Chrome pass driven over the DevTools Protocol assert the modal focus trap under real Tab presses, focus restore to the trigger, browser-enforced inert on the background, roving-tabindex arrow navigation, a tooltip that opens on focus, and the toast timer pausing and resuming. Includes a backdrop-filter @supports fallback that drops to opaque surfaces, a contrast scrim with a high-contrast escalation, prefers-reduced-motion handling on every animation, and dark mode driven entirely by tokens. The declared React 18.3 / 19 peer range is exercised on both majors rather than merely declared. Ships a runnable Vite demo, a CI workflow and a changelog; the README documents the contrast, tooltip-positioning and Chrome-only-coverage trade-offs rather than glossing over them.
Realtime WebSocket Notification Drawer
A notification drawer built from a resilient WebSocket client, an accessible shadow-DOM web component and a matching demo server, with no runtime dependencies on either side. The client handles jittered exponential-backoff reconnect, application-level heartbeats, an outbound queue that survives disconnection, de-duplication by id, at-least-once acks and resume-from-last-seen-id. The server is a hand-written RFC 6455 implementation on node:http covering the Sec-WebSocket-Accept handshake, frame masking, 16- and 64-bit payload lengths, continuation frames, close codes and ping/pong, plus a topic broadcast hub and a POST /publish endpoint. The drawer's focus trap, keyboard navigation, aria-live announcements, style isolation and reconnect behaviour are exercised in headless Chrome by an included test suite that drives the DevTools Protocol directly. It does not support permessage-deflate, the hub is in-memory and single-process, and the drawer list is capped rather than virtualised.