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

@buggyorg/nitro

v0.3.0

Published

An optimizer for Buggy control flow graphs.

Downloads

17

Readme

Nitro

Nitro is an optimizer for Buggy programs that uses graph rewriting.

CLI

You need to install Nitro with npm i -g @buggyorg/nitro in order to use it. The following options are available:

-f, --graphfile <graph file>   Set graph file to parse. If none is given stdin is read
-o, --out <graph output file>  Set a custom output file. If none is given, stdout is used.
-i, --include-intermediate     Print an array of all intermediate graphs.
--stats                        Print stats to stderr after optimizing the graph.
-v, --verbose                  Prints verbose output to stderr during optimization.
--keep-dead-code               Disable removal of unreachable code.
-h, --help                     Output usage information.
-V, --version                  Output the version number.

Example usage: nitro -f program.json --stats -v -o program_optimized.json

API

You can use Nitro (or maybe certain rewrite rules) easily using the its API.

import { optimize, applyRule, rewriteRules } from '@buggyorg/nitro'
  • optimize(graph, options = {})
    Optimize the given Buggy port graph (as graphlib graph). Returns an object { graph, stats } with graph being the optimized graph and stats being statistics about the optimization.

    Supported options:

    • rules: Array of the rewrite rules to use, defaults to all rewrite rules.
    • keepDeadCode: Whether to disable the rewrite rules that remove dead code, only works if rules is not specified.
    • onRuleApplied: A function that is called whenever a rewrite rule was applied. The only argument it is called with is the used rewrite rule.
  • applyRule(graph, rule)
    Apply a single rewrite rule on the given graph. Returns true if the rule changed the graph and false if it didn't.

  • rules
    An object-map of the available rewrite rules. The keys are the IDs of the rules that may be used in the options above.