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

@lune-js/context

v1.0.0

Published

Optimized context library to manage state and behavior in Lune.js

Readme

@lune-js/context

Optimized context library to manage state and behavior in Lune.js.

NOTE

This package is published only for typing and building custom renderers in Lune.js. It is NOT recommended to install as a standalone package.

Expressions

The expression engine lives here. evaluate runs a single expression and execute runs a statement list, both against a scope and an optional element. Sources go through this package's own lexer, parser and compiler rather than the Function constructor, so a renderer built on it inherits the CSP compatibility described in lune-js, which also documents the supported language subset and the identifier resolution order.

Two pieces of state belong to the module rather than to a Context:

  • The compiled expression cache, keyed by source text. A source compiled while rendering one context is reused by every other context in the same copy of the package.
  • The registry written by allowGlobals, which adds identifiers the engine resolves last, after locals, the scope and the $el/$data aliases. It is engine wide because identifier resolution runs with a scope and an element in hand and never a context, so a registration has no app or context to be scoped to. A value that should reach one app only belongs in that app's scope instead. See Application globals for the full semantics.