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

@gwigz/tstl-bundle-flatten

v1.4.0

Published

TSTL plugin that flattens luaBundle output, eliminating the module system

Downloads

450

Readme

@gwigz/tstl-bundle-flatten

A TypeScriptToLua plugin that flattens luaBundle output, eliminating the module system entirely.

TSTL's bundler wraps each module in a closure with a require() runtime. This plugin rewrites the bundle to emit all module code in dependency order as top-level locals, removing the ____modules table, ____moduleCache, require() function, module closures, and import/export boilerplate.

When is this useful?

Some Lua runtimes don't support or benefit from a module system, or are have tight limitations. If you're targeting an environment like this and using luaBundle, the generated runtime adds unnecessary overhead. This plugin strips it out and gives you clean, top-level code.

Install

bun add -D @gwigz/tstl-bundle-flatten
# or
npm install -D @gwigz/tstl-bundle-flatten

Setup

Add the plugin to your tsconfig.json:

{
  "tstl": {
    "luaBundle": "bundle.lua",
    "luaBundleEntry": "src/index.ts",
    "luaPlugins": [
+     { "name": "@gwigz/tstl-bundle-flatten" }
    ]
  }
}

Options

Options are passed inline in the plugin entry:

{
  "name": "@gwigz/tstl-bundle-flatten",
  // Modules to exclude from flattening (kept in the bundle runtime)
  "skipModules": ["constants"],
  // Insert blank lines at code boundaries for readability (default: true)
  "format": true,
  // Remove unused code after flattening, requires darklua-wasm (default: false)
  "shake": false,
}

| Option | Type | Default | Description | | ------------- | ---------- | ------- | -------------------------------------------------------- | | skipModules | string[] | [] | Module names to leave untouched by the flattener | | format | boolean | true | Add whitespace between logical code blocks in the output | | shake | boolean | false | Remove unused top-level code after flattening |

Tree shaking

Flattening turns every module export into a top-level local, which makes dead code elimination simple: anything nothing references can be removed. With "shake": true, the plugin runs darklua's remove_unused_variable and remove_empty_do rules over the flattened output.

This requires the optional darklua-wasm peer dependency:

bun add -D darklua-wasm
# or
npm install -D darklua-wasm

What it does:

  • Removes unused local function definitions and unused locals, including functions only referenced by other removed functions
  • Keeps side effects: an unused local x = call() becomes a bare call()
  • Shakes inlined lualib functions too, since they flatten into locals like everything else

Unlike TypeScript-level tree shaking, this happens after bundling, so it also catches unused exports pulled in through re-export chains (barrel files).

Source maps

With "sourceMap": true in your compilerOptions, the plugin rewrites the emitted .map alongside the code, so generated lines still resolve back to the original TypeScript after flattening, shaking and formatting.

Mapping is line accurate, not column accurate: the transforms rewrite line contents, so only the line a statement ended up on is meaningful. That is enough to turn a runtime or compiler error in the flattened output back into a file and line you recognise.

TSTL writes the map before plugins run, so without this the .map on disk would describe the unflattened bundle and point at the wrong lines.

inlineSourceMap is not supported: TSTL appends its comment after the bundle's entry call, which flattening drops along with the rest of the module runtime.

Example

Given a bundle with two modules:

src/
├── greet.ts → export function greet(name: string) { ... }
└── index.ts → import { greet } from "./greet"

TSTL's default luaBundle output wraps everything in a module runtime. After tstl-bundle-flatten, you get:

local function greet(name)
  print("Hello, " .. name)
end

greet("world")

No ____modules, no require, no closures, just flat Lua.