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

@lankajs/react

v0.2.0

Published

module: One hook — `useLankaVM` — and the access tracking core already does.

Downloads

57

Readme

@lankajs/react

▸ module · React binding

One hook — useLankaVM — and the access tracking core already does.

A library in the same box. The app imports and calls it; core does not know it exists.

Runs in: the browser and React Native.

Requires: React. Enforced by check-runtime.mjs, which refuses an import of any other.

How to use it: GUIDE.md — the user guide, with examples. How to change it: SKILL.md.

Contents

  • useLankaVM — the one name, and the same one every member of this shelf publishes
  • core's six ViewModel factories, under core's own names and already wearing this framework's read — a declaration moves by its import line
  • toLankaCallableVM — the same read applied to a ViewModel this package did not declare: a class, a library's, or one core built
  • renderWithLanka (from @lankajs/react/testing) — a render with a bootstrapped framework

What this package is, and what it deliberately is not

It is a subscription and a render trigger. The ACCESS TRACKING — which state keys a component read, and whether a change touched them — is createLankaAccessTracker in core, published through lanka/extend, and every binding on this shelf calls it. That is why the behaviour a consumer sees is the framework's rather than each binding's re-reading of it, and it is what lankaViewBindingConformance checks.

So the whole of useLankaVM is a ref, a stable subscribe and useSyncExternalStore. If it ever needs more than the port gives it, the port is the thing with the defect.

"use client" is here and not in core

React Server Components make an import of a hook a build error. Core has no hook any more, so lanka/viewmodel is server-safe and this barrel carries the directive — which is the split doing its job: a Next application's server components may read a ViewModel's state, and only the components that RENDER it are client components.

One binding for React and React Native

useSyncExternalStore is React's, not the DOM's. Expo installs this package and nothing else changes — which is also why runtime says browser, native and not node.


Repository map: ../../../README.md