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

@seokgukim/mlua-language-server

v1.0.1

Published

Standalone LSP server for the mLua language (MapleStory Worlds scripting). Wraps the msw.mlua VS Code extension and exposes a standard stdio JSON-RPC interface compatible with any LSP client.

Readme

mlua-language-server

Standalone LSP server for the mLua language (MapleStory Worlds scripting).

Wraps the msw.mlua VS Code extension and exposes a standard stdio JSON-RPC interface compatible with any LSP client (Neovim, Zed, Helix, etc.).

Requirements

  • Node.js >= 16

Installation

npm install -g mlua-language-server

Or clone and use directly:

git clone https://github.com/...
cd mlua-language-server
node mlua-server.js --stdio

Usage

mlua-language-server --stdio

The extension (msw.mlua) is downloaded automatically from the VS Code Marketplace on first run. Subsequent runs use the cached copy.

To pin a specific install directory:

MLUA_INSTALL_DIR=/path/to/msw.mlua-1.1.5 mlua-language-server --stdio

Editor Setup

Neovim

Use mlua.nvim which bundles this wrapper and handles setup automatically.

For manual setup with nvim-lspconfig:

vim.lsp.config('mlua', {
  cmd = { 'mlua-language-server', '--stdio' },
  filetypes = { 'mlua' },
  root_dir = function(bufnr, on_dir)
    -- point to your project root
    on_dir(vim.fn.getcwd())
  end,
})
vim.lsp.enable('mlua')

Zed

Add to settings.json:

{
  "lsp": {
    "mlua": {
      "binary": {
        "path": "mlua-language-server",
        "args": ["--stdio"]
      }
    }
  }
}

Helix

Add to languages.toml:

[[language]]
name = "mlua"
language-servers = ["mlua-language-server"]

[language-server.mlua-language-server]
command = "mlua-language-server"
args = ["--stdio"]

Project Root Detection

The server indexes the entire project on startup. The project root is determined from the rootUri sent by the editor, with the following logic:

  1. If the given directory (or any ancestor) contains both a RootDesk/ and an Environment/ sibling, that ancestor is used as the project root.
  2. Otherwise the directory sent by the editor is used as-is.

This ensures Environment/NativeScripts/ (type definitions) is always included in the workspace index regardless of which subdirectory the editor reports as the root.

How It Works

Editor  ──stdio──▶  mlua-server.js  ──▶  proxy.js  ──stdio──▶  languageServer.js
                       (entry)             (LSP bridge)          (msw.mlua engine)

proxy.js intercepts the LSP initialize request, resolves the project root, indexes all .mlua and entry files (.map, .ui, .model, .collisiongroupset), and injects the result into initializationOptions before forwarding to the language server engine.

File watching is set up for the resolved project root so entry file changes (.ent) are forwarded to the server in real time.

Environment Variables

| Variable | Description | |---|---| | MLUA_INSTALL_DIR | Absolute path to the msw.mlua-<version>/ directory. Skips auto-discovery. |