npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rrjs/react-compat

v0.1.0

Published

React hooks API on top of signals: useState, useEffect, useReducer, useContext, and more

Downloads

164

Readme

@rrjs/react-compat

React hooks implemented on top of signals. Designed so React code translates with minimal changes: state is read through a getter (count() instead of count). Inside JSX the Babel plugin handles this automatically.

Install

npm install @rrjs/react-compat @rrjs/signals @rrjs/renderer

Quick start

import { useState, useEffect, useMemo } from '@rrjs/react-compat'
import { h, mount } from '@rrjs/renderer'

function Counter() {
  const [count, setCount] = useState(0)
  const doubled = useMemo(() => count() * 2, [count])

  useEffect(() => {
    document.title = `Count: ${count()}`
  }, [count])

  return h('div', null,
    h('p', null, () => `${count()} → ${doubled()}`),
    h('button', { onClick: () => setCount(count() + 1) }, 'inc')
  )
}

mount(Counter, document.getElementById('app'))

Supported hooks

| Hook | Status | Notes | |---|---|---| | useState | ✓ | Returns [getter, setter]. Functional updaters supported. | | useReducer | ✓ | Returns [stateGetter, dispatch]. Lazy init supported. | | useMemo | ✓ | Returns a getter. Wrapped in computed — auto-tracks signals read inside. | | useCallback | ✓ | Standard React behavior with dep array. | | useEffect | ✓ | Fires post-paint via MessageChannel. Cleanup runs before next effect. | | useLayoutEffect | ✓ | Fires synchronously before paint. | | useRef | ✓ | Plain mutable box. | | useContext | ✓ | Stack-based propagation. createContext + Provider. | | useId | ✓ | Generates :rN:-style ids. Client-only. | | useImperativeHandle | ✓ | Pairs with forwardRef. | | useSyncExternalStore | ✓ | Subscribes to external stores (Redux, Zustand, etc.). | | useDeferredValue | — | No-op; returns input as-is. | | useTransition | — | No-op; runs synchronously. |

Forwarding refs

import { forwardRef, useRef } from '@rrjs/react-compat'

const FancyInput = forwardRef((props, ref) =>
  h('input', { ref, type: 'text', ...props })
)

function Form() {
  const inputRef = useRef(null)
  return h(FancyInput, { ref: inputRef })
}

Context

import { createContext, useContext } from '@rrjs/react-compat'

const ThemeContext = createContext('light')

function App() {
  return h(ThemeContext.Provider, { value: 'dark' },
    h(ThemedButton, null)
  )
}

function ThemedButton() {
  const theme = useContext(ThemeContext)
  return h('button', { className: theme }, 'click')
}

Nested providers are supported. Each Provider push is paired with a pop after children mount.

External stores (Redux, Zustand, etc.)

import { useSyncExternalStore } from '@rrjs/react-compat'

function Counter({ store }) {
  const state = useSyncExternalStore(store.subscribe, store.getState)
  return h('div', null, () => state().count)
}

Same contract as React 18+. Any state library that ships React bindings using useSyncExternalStore should work.

Why getters instead of values

In React, const [count, setCount] = useState(0) makes count a plain number. That works because React re-runs the entire component function on every state change — the new value of count comes from the new render.

In a signal model, the component runs once. After that, count would be frozen at the initial value forever. To stay reactive without re-running the component, count must be a function that reads the live signal. So count is a getter: count().

Inside JSX, the Babel plugin wraps {count} as () => count, and the renderer auto-invokes nested getters. So in JSX you write {count} the same as in React. Outside JSX (event handlers, useMemo factories, useEffect bodies), you call the getter: count().

License

MIT License

Copyright (c) 2026 Saman Abaasi

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.