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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@levimc-lse/scaffold

v1.0.0

Published

A utility for assisting in the development of Legacy Script Engine plugins.

Readme

Legacy Script Engine Scaffold

English | 简体中文

A utility for assisting in the development of Legacy Script Engine plugins, supporting a native development experience on the Node.js platform.

Only TypeScript projects are supported at the moment.

📦 Prepare

It is a non-intrusive tool, meaning it does not require any mandatory files to be kept in your project. However, it is recommended to add it as a development dependency to your environment for convenient usage:

npm install @levimc-lse/scaffold --save-dev

🚀 Usage

Generate manifest.json for the Legacy Script Engine plugin

npx lses manifest

Package the Legacy Script Engine plugin

npx lses pack

Deploy the Legacy Script Engine plugin package to the LeviLamina server by path

npx lses deploy-path <path> [options]

| Argument | Description | Type | |----------|-----------------------------------------------|--------| | <path> | Specific LeviLamina server working directory. | String |

| Option | Description | Type | Default | |------------------------------------| -------------------------------- | ------- | ------- | | -h, --host <remote-host> | Remote Windows OpenSSH host. | String | | | -P, --port <remote-port> | Remote Windows OpenSSH port. | Integer | 22 | | -u, --username <remote-username> | Remote Windows OpenSSH username. | String | | | -p, --password <remote-password> | Remote Windows OpenSSH password. | String | |

Launch a LeviLamina server as a debugger

npx lses debug <path> <name> [options]

| Argument | Description | Type | | -------- | --------------------------------------------- | ------ | | <path> | Specific LeviLamina server working directory. | String | | <name> | Alias name for the debugger instance. | String |

| Option | Description | Type | Default | |------------------------------------| -------------------------------- | ------- | ------- | | -h, --host <remote-host> | Remote Windows OpenSSH host. | String | | | -P, --port <remote-port> | Remote Windows OpenSSH port. | Integer | 22 | | -u, --username <remote-username> | Remote Windows OpenSSH username. | String | | | -p, --password <remote-password> | Remote Windows OpenSSH password. | String | |

Deploy the Legacy Script Engine plugin package to the LeviLamina server debugger instance

💡 Key Feature

Compared to npx lses deploy-path, this deployment method automatically hot reloads the plugin.

npx lses deploy-debug <debugger-name>

| Argument | Description | Type | |-------------------| -------------------------------------------------- | ------ | | <debugger-name> | Specific LeviLamina server debugger instance name. | String |

❗ Important

  1. The main configuration entry file in package.json should be relative to the project's working directory, not the directory of the Legacy Script Engine plugin package.

    For example, in a TypeScript project where index.ts is defined as the entry point in source code and the TypeScript compiler is configured via tsconfig.json to emit to the build directory named dist, you should set the main field in package.json to dist/index.js.

    This ensures that the entry field in the manifest.json generated by npx lses manifest can be correctly identified and located by LeviLamina.

  2. Ensure that the corresponding LeviLamina server debugger instance exists before using npx lses deploy-debug, so need to launch it first using npx lses debug.