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

@urk/react-urk

v0.1.1

Published

URK React wrapper - thin provider and hooks around an existing kernel

Readme

@urk/react-urk

Thin React bindings for consuming an existing URK kernel instance.

If you are consuming URK inside a Next App Router client boundary, prefer @urk/next-urk on top of this package instead of rebuilding that boundary yourself.

This package stays wrapper-only:

  • it accepts an existing Kernel
  • it subscribes to RuntimeStore
  • it exposes the kernel event bus
  • it does not introduce a React-owned runtime model

Public API

  • UrkProvider
  • useKernel()
  • useRuntimeSnapshot()
  • useRuntimePhase()
  • useRuntimeInspector()
  • useRuntimeInspectorSnapshot()
  • useEventBus()
  • useKernelEvent()
  • KernelEventListener

Usage

import { useMemo } from 'react';
import { createKernel } from '@urk/core';
import { createLoadingAdapter } from '@urk/adapters/dom';
import { UrkProvider, useKernelEvent, useRuntimeInspectorSnapshot, useRuntimePhase } from '@urk/react-urk';

function RuntimeView() {
  const phase = useRuntimePhase();
  const inspector = useRuntimeInspectorSnapshot();

  useKernelEvent('runtime:paused', (event) => {
    console.log(event.type);
  });

  return <div>{phase} / {inspector.frameCount}</div>;
}

export function App() {
  const kernel = useMemo(() => {
    return createKernel({
      adapters: [createLoadingAdapter()],
    });
  }, []);

  return (
    <UrkProvider kernel={kernel}>
      <RuntimeView />
    </UrkProvider>
  );
}

UrkProvider auto-boots by default. It only shuts the kernel down on unmount when the provider was responsible for booting the kernel in the first place.

This package is validated through type-check/build plus the private React proof route in examples/react-starter/, including wrapper-facing runtime inspector consumption.