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

@lostcityrs/runescript

v0.9.6

Published

Compiler for a community-derived RuneScript implementation, written in TypeScript

Downloads

935

Readme

This is a RuneScript Compiler, written in TypeScript. Our focus is to preserve RS2 history as accurately and authentically as we can.

Installation and Usage

npm i @lostcityrs/runescript
(or yarn, bun, pnpm...)

import { CompileServerScript, CompilerTypeInfo } from '@lostcityrs/runescript';

// opcode->command lookup + pointer info
const commandInfo: CompilerTypeInfo = ...;

// script id->name lookup
const runescriptInfo: CompilerTypeInfo = ...;

// config id->name lookup
const npcInfo: CompilerTypeInfo = ...;

CompileServerScript({
    symbols: {
        'command': commandInfo,
        'runescript': runescriptInfo,

        'npc': npcInfo,
        ...
    }
});

The compiler expects a couple things to be in place.

  1. A source folder that contains .rs2 scripts.
  2. Symbol information provided for the types you plan on referencing.

By default it will read scripts from ../content/scripts. After it runs, compiled output will be placed in ./data/pack/server.
If that doesn't work for your use case, please see the config object you pass to CompileServerScript.

See LostCityRS/Server for a working example.

Building RuneScriptTS

After cloning:

bun i
bun run antlr

Testing:
You can test changes without publishing by copying dist/runescript.js into your consumer's node_modules folder

bun run build
cp dist/runescript.* ../node_modules/@lostcityrs/runescript/dist/

History

Originally a fork of Neptune's script compiler.
Our initial compiler fork (2023-2026) focused instead on making a complete server script compiler, along with a script runtime and world simulation:
https://github.com/LostCityRS/RuneScriptKt
https://github.com/LostCityRS/Engine-TS

As of February 2026 we have transitioned from the "legacy" Kotlin codebase to this TypeScript codebase (clean port).
Consumers should use this. It is production-ready and produces compatible output along with some bug fixes.

Credits

Polar: For your years of work on Neptune and many days brainstorming together.
Flenarn: For your effort porting so much Kotlin code to TypeScript. There were only a few lines to fix afterwards - great job.
Contributions in RuneScriptKt: Henke96 PR #1 and Bea5 PR #2.