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

pterospeed

v0.4.0

Published

CLI to analyze and optimize Pterodactyl panel build performance.

Readme

pterospeed

Cut your Pterodactyl Panel build time from 5 minutes to under 90 seconds — no manual webpack knowledge required.

npm license


The problem

Every Pterodactyl dev knows this:

webpack 5 compiled successfully in 347210 ms
Done in 352.41s.

The default webpack config that ships with Pterodactyl Panel is unoptimized. No filesystem cache, no transpile cache, slow production minifier, no CPU parallelism. Every build starts cold and pays the full cost.

pterospeed finds those issues and fixes them — automatically, with a diff preview and a backup before touching anything.


Usage

# Run directly, no install needed
npx pterospeed@latest .

# Or install globally
npm i -g pterospeed

Commands

pterospeed [path]                               # analyze (default)
pterospeed analyze [path]                       # scan config and report score
pterospeed optimize [path]                      # diff → confirm → apply
pterospeed optimize [path] --auto               # skip confirmation
pterospeed optimize [path] --dry                # diff only, write nothing
pterospeed optimize [path] --preset aggressive  # also swap TerserPlugin → esbuild
pterospeed benchmark [path]                     # measure cold / warm / production builds
pterospeed revert [path]                        # restore last backup

What it fixes

Safe preset (default)

| Optimization | Expected gain | |---|---| | Webpack filesystem cache | Warm builds 5–10x faster — skips full cold parse | | babel-loader disk cache | Cold builds ~20–30% faster — no re-transpile of unchanged files | | Scope source-map-loader | Skips parsing maps inside node_modules | | Explicit CPU parallelism | Full core utilization on multi-core hosts |

Aggressive preset (--preset aggressive)

Everything in safe, plus:

| Optimization | Expected gain | |---|---| | EsbuildPlugin instead of TerserPlugin | Production minification ~3–4x faster |

After aggressive optimization, run yarn install (or npm install) in your panel to install esbuild-loader.


How it works

pterospeed reads your webpack.config.js as an AST using recast. It makes surgical edits on the syntax tree — no string replacement, no regex. Your formatting and comments stay intact.

Before writing anything, it saves a timestamped backup to .pterospeed/backups/. Run pterospeed revert at any time to undo.


Requirements

  • Node.js 20+
  • A project with webpack.config.js (Pterodactyl Panel, Pelican, or any webpack 5 project)

Roadmap

  • [ ] v0.2 — Pelican Panel support
  • [ ] v0.3 — swap babel-loader for esbuild-loader entirely (aggressive)
  • [ ] v0.4 — thread-loader support
  • [ ] v0.5pterospeed migrate-vite: full webpack → Vite migration with blade template patching, backup, and dry-run
  • [ ] v1.0 — general webpack optimizer, any project

Contributing

See CONTRIBUTING.md.


License

MIT © Molret


⭐ Star this repo if it saved you time.