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

nola-lang

v0.1.4

Published

The Nola language toolchain: nola init/build/run/check and the Node loader for .tsi files

Downloads

866

Readme

nola-lang

The Nola toolchain. Nola is a TypeScript superset (.tsi) where infer functions and ask extractors turn prompts into typed values, resolved by a configured LLM at run time.

Install as a devDependency — your app depends on @nola-lang/runtime and @nola-lang/providers instead (the scaffold sets all of this up):

npm create nola my-app          # or: npx nola init

Commands

nola init [dir]                 scaffold a new Nola project
nola build [dir] [--out dist]   compile .tsi -> js + source maps + d.ts
nola run <entry>                run a .tsi/.ts entry with the loader + nola.config.ts
nola check [dir]                type-check .tsi and .ts together, positions mapped back

Direct node execution (the tsx model)

node --import nola-lang/register src/main.tsi

The loader inlines source maps pointing at the on-disk .tsi, so VS Code breakpoints bind directly in Nola source.

Production builds

nola build output is self-contained: for app projects (the default) it emits dist/nola.config.js — your bundled config — and wires every built module to load it, so node dist/<entry>.js needs no loader and no manual nolaRuntime.configure(). Library authors set build: { target: "lib" } in nola.config.ts to skip that wiring; the consuming app configures the process. Provider secrets come from the real environment in production — .env files are a dev-time convenience.