A thorough utility toolkit for profiling HTTP request execution. Track runs, analyze performance, generate reports, compare results, and export data — all from the command line with local storage.
All commands accept optional <input> arguments. Without arguments, they display recent entries from their log.
CommandDescriptionweb-profiler-bundle run <input>Run a profiling task and log the resultweb-profiler-bundle check <input>Check an endpoint, middleware, or configurationweb-profiler-bundle convert <input>Convert profiling data between formatsweb-profiler-bundle analyze <input>Analyze request timing, memory usage, or query breakdownsweb-profiler-bundle generate <input>Generate profiling configs, reports, or templatesweb-profiler-bundle preview <input>Preview profiling output before committingweb-profiler-bundle batch <input>Batch process multiple profiling operationsweb-profiler-bundle compare <input>Compare two profiling results side by sideweb-profiler-bundle export <input>Log an export operationweb-profiler-bundle config <input>Log or update configuration entriesweb-profiler-bundle status <input>Log a status check resultweb-profiler-bundle report <input>Generate or log a report entryweb-profiler-bundle statsShow summary statistics across all log filesweb-profiler-bundle export json|csv|txtExport all data in JSON, CSV, or plain text formatweb-profiler-bundle search <term>Search across all log entries for a keywordweb-profiler-bundle recentShow the 20 most recent activity entriesweb-profiler-bundle helpShow all available commandsweb-profiler-bundle versionPrint version (v2.0.0)
All data is stored locally in ~/.local/share/web-profiler-bundle/. Each command maintains its own .log file with timestamped entries in YYYY-MM-DD HH:MM|value format. A unified history.log tracks all operations across commands.
Export formats supported:
type, time, and value fieldstype,time,value headerset -euo pipefail (strict mode)date, wc, du, grep, tail, sed, catbash
# Profile a specific route
web-profiler-bundle run "POST /api/orders — 580ms, 24MB, 47 queries"
# Analyze query breakdown
web-profiler-bundle analyze "N+1 detected: users.orders — 34 queries, 210ms total"
# Compare before and after optimization
web-profiler-bundle compare "cache warm: 120ms vs cold: 890ms"
# Check middleware stack
web-profiler-bundle check "auth middleware — 12ms overhead"
# Export all profiling data to JSON
web-profiler-bundle export json
# Search for memory-related entries
web-profiler-bundle search "memory"
# View summary statistics
web-profiler-bundle stats
Web Profiler Bundle stores all data locally in ~/.local/share/web-profiler-bundle/. Each command creates a dedicated log file (e.g., run.log, analyze.log, report.log). Every entry is timestamped and appended, providing a full audit trail of all profiling activity. The history.log file aggregates operations across all commands for unified tracking.
When called without arguments, each command displays its most recent 20 entries, making it easy to review past profiling work without manually inspecting log files.
All output goes to stdout. Redirect to a file with:
bash
web-profiler-bundle stats > report.txt
web-profiler-bundle export json # writes to ~/.local/share/web-profiler-bundle/export.json
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com