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

lua-compile

v1.0.2

Published

Compile lua to a single file

Readme

Compiled Require

This compiler strives to emulate the native require method as accurately as possible, while exposing an api that allows modules to mutate imports

A compiler designed to compile multiple files into one with full lua support. Specifically for Tabletop Simulator

Also, due to the lack of a runtime, all paths have to be parsed by the compiler. (Though a custom compiler could be made to target a specific runtime) This means require statements must be passed a string literal. Alternatively, the file can use #include headers to specify paths to the compiler

Ideal compiler

  • Can be decompiled with full accuracy
    • For simplicity's sake, it would be nice to leave source intact
  • require is always local to the contents of the file
    • Obviously this isn't really 'perfect' - real require doesn't follow packages. But thats dumb. So we will.
  • All require statements will resolve properly. string literal or not
  • require statements found in the file will be used for discovery.
    • It's not even close to practical to resolve require statements without string literals, so instead the compiler will provide a warning to allow the user to add it manually.
      • This could be done with file headers like --## require "os"