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/angular

v0.2.0

Published

module: One function — `useLankaVM` — over a signal, and the access tracking core already does.

Readme

@lankajs/angular

▸ module · Angular binding

One function — useLankaVM — over a signal, 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.

Requires: Angular. 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

What an Angular call answers

A Signal: state().rows in a component, {{ state().rows }} in a template. Zoneless works with no extra step, because a signal is what zoneless change detection reads.

The injection context, and why it is required rather than optional

useLankaVM must be called where Angular can inject — a constructor, a field initialiser, a factory, or inside runInInjectionContext. It asserts that, and the message names the fix.

That is stricter than the Vue and Solid bindings, which publish a stop() for a call made outside their scope. Angular's reason is different: DestroyRef is the ONLY way to know when the caller goes away, and a subscription with no way to learn that is a leak with no owner. Where Vue and Solid degrade, Angular refuses — and refusing at the call is better than a leak discovered in production.

The injection context reaches a test too

renderWithLanka from @lankajs/angular/testing renders a component with a live framework behind it, the way every other member of this shelf does. What differs is underneath: Angular Testing Library drives TestBed, so a component here is compiled rather than merely mounted — and a ViewModel read in a field initialiser is inside an injection context, which is the one thing this binding insists on.


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