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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@moonlight-mod/lunast

v1.0.0

Published

Experimental AST processor for the Discord client's Webpack modules.

Downloads

49

Readme

LunAST

Experimental AST processor for the Discord client's Webpack modules.

Usage

LunAST functions off of "processors". A processor has a unique ID, priority, an optional filter, and a process function. These must be registered in your index.ts file ASAP - not in a Webpack module or on the Node/host sides.

moonlight.lunast.register({
  name: "UniqueIDForTheProcessor",
  find: "something to look for",
  process(state) {
    return false;
  }
});

When a find is specified, the AST parsing will only be done on modules that match that regex/string(s). find is highly suggested, as AST parsing is much more expensive than simple string checks.

The process function will be called for every matched module. The state argument contains the LunAST instance, the ID of the matched module, some utilities, and more. When process returns true, the processor is unregistered, and will not trigger for future modules. Return true when you have found your desired module(s).

Utilities

There are various utilities accessible through state.lunast.utils.

You can use the magicAST function to turn some JavaScript code into another AST node, and then merge/replace the original AST. After you modify the AST, call the markDirty function. LunAST will not know to replace the module otherwise. It is suggested you read the estree-toolkit documentation.

process({ ast, markDirty, lunast }) {
  const node = /* do something with the AST */;
  if (node != null) {
    const replacement = lunast.utils.magicAST("return 1 + 1");
    node.replaceWith(replacement);
    markDirty();
    return true;
  }

  return false;
}

Embedding into client mods

First, create an instance of LunAST:

import LunAST from "@moonlight-mod/lunast";
const lunast = new LunAST();

Expose this instance to your extensions (before Webpack initializes) so extensions can register custom processors.

You'll then need to set a module source getter, so LunAST can retrieve the source of other modules.

lunast.setModuleSourceGetter((id) => {
  // assuming `funcs` is a Record<string, WebpackModuleFunc>
  return funcs[id].toString().replace(/\n/g, "");
});

Then, when processing a module into the Webpack chunk, give it the script to parse and patch the returned modules:

const parsed = lunast.parseScript(id, code);
if (parsed != null) {
  for (const [id, script] of Object.entries(parsed)) {
    // Patch module `id` with the contents of `script`
  }
}

TODO

  • [x] Publish
  • [ ] Release to NPM