pterospeed analyzes your webpack config, finds what's slowing it down, and fixes it — automatically, with a diff preview and backup before touching anything.
npx pterospeed@latest . no install required · Node 20+
The problem
The default webpack config that ships with Pterodactyl Panel was written to work, not to be fast. Every build starts from zero and pays the full cost.
$ yarn build:production
webpack compiled successfully in
352.41s
after pterospeed optimize --preset aggressive
~78s
same output · no code changes
How it works
1 — analyze your config
2 — apply the fixes
Optimizations
| Optimization | Preset | Expected gain |
|---|---|---|
| Webpack filesystem cache | safe | Warm builds 5–10× faster |
| babel-loader disk cache | safe | Cold builds ~20–30% faster |
| Scope source-map-loader | safe | Skips node_modules map parsing |
| Explicit CPU parallelism | safe | Full core utilization |
| minimize: isProduction | safe | Dev skips minification (~30-60s) |
| EsbuildPlugin (prod) | aggressive | Production minify 3–4× faster |
After aggressive preset: run yarn install in your panel to install esbuild-loader.
CLI
pterospeed analyze [path] Scan config and report score pterospeed optimize [path] Diff → confirm → apply fixes pterospeed optimize --auto Skip confirmation prompt pterospeed optimize --dry Show diff only, write nothing pterospeed optimize --preset aggressive Also swap TerserPlugin → EsbuildPlugin pterospeed benchmark [path] Measure cold / warm / production builds pterospeed revert [path] Restore last backup Run it right now — no install, no config, no risk. Backup created before touching anything.
npx pterospeed@latest .