TraceGL alternatives and similar modules
Based on the "Debugging / Profiling" category.
Alternatively, view TraceGL alternatives based on common mentions on social networks and blogs.
node-inspector8.8 0.0 L2 TraceGL VS node-inspectorNode.js debugger based on Blink Developer Tools
ndb8.5 0.0 TraceGL VS ndbndb is an improved debugging experience for Node.js, enabled by Chrome DevTools
devtool6.9 0.0 L5 TraceGL VS devtool[OBSOLETE] runs Node.js programs through Chromium DevTools
0x6.4 6.2 L2 TraceGL VS 0x🔥 single-command flamegraph profiling 🔥
ironNode6.0 0.0 L4 TraceGL VS ironNodeDebug Node.js code with Chrome Developer Tools.
leakage5.6 4.2 TraceGL VS leakage🐛 Memory leak testing for node.
why-is-node-running5.5 2.5 L5 TraceGL VS why-is-node-runningNode is running but you don't know why? why-is-node-running is here to help you.
swagger-stats4.9 0.0 TraceGL VS swagger-statsAPI Observability. Trace API calls and Monitor API performance, health and usage statistics in Node.js Microservices.
longjohn4.7 0.0 TraceGL VS longjohnLong stack traces for node.js inspired by https://github.com/tlrobinson/long-stack-traces
njsTrace3.6 0.0 L5 TraceGL VS njsTraceA Node.js tracing and instrumentation utility
locus3.1 0.0 TraceGL VS locusLocus is a debugging module for node.js
stackman2.6 0.0 L5 TraceGL VS stackmanHe is like Batman, but for Node.js stack traces
NiM2.6 3.8 TraceGL VS NiMStreamline Your Node.js Debugging Workflow with Chromium (Chrome, Edge, More) DevTools.
thetool2.5 0.0 TraceGL VS thetoolthetool is a CLI tool to capture different cpu, memory and other profiles for your node app in Chrome DevTools friendly format
bugger2.3 0.0 L4 TraceGL VS buggerBugs bugging you? Bug back.
vstream2.2 0.8 L5 TraceGL VS vstreaminstrumented streams
ctrace1.9 0.0 L3 TraceGL VS ctraceWell-formatted and improved trace system calls and signals (when the debugger does not help)
dats1.5 8.7 TraceGL VS dats📈 Minimalistic zero-dependencies statsd client for Node.js
Appwrite - The Open Source Firebase alternative introduces iOS support
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of TraceGL or a related project?
TraceGL MPL release (C) Mozilla Corp
Running traceGL unpackaged:
git clone [email protected]:/traceglMPL/tracegl.git cd tracegl node trace/trace_server.js
Packaging tracegl into a single JS file you can copy everywhere (like your home dir)
node tools/packer.js trace/trace_server tracegl.js cp tracegl.js ~/
How it works
node ~/tracegl [options] yourprogram.js [arguments]
The visualisation UI is available on http://localhost:2000.
Browser JS via static fileserver
node tracegl [options] ../path/to/wwwroot
Browser JS via proxy
node tracegl [options] http://localhost:3000
By doubleclicking on a line in the visualisation UI you can open it in your favorite editor. See the settings for information how to configure this
node ~/tracegl [options] target [args]
target can be 1. a node.js program, 2. a static folder, 3. a proxy target or 4. a gzip file created with -gz to playback.
options can be:
-gz[:trace.gz] Record a trace to gzip file, defaults to trace.gz, doesn't start the UI.
Filtering can be useful to lower the amount of incoming tracedata. Use -do and -no with either a -do:string or a -do/regex match. Use double escaped backslashes in regexps (see -nolib).
-do[/:]match Only trace files where filename contains match.
-no[/:]match Don't trace files where filename names contains match.
-nolib Only see your own code. Short for: -no/jquery.* -no:require.js -no/node\_modules
-noopen Don't try to open the visualisation UI with your default browser
-ui:port Explicitly set the visualisation UI port, default is 2000
-tgt:port Explicitly set the browser JS port, defaults to 2080
-settings Write a settings tracegl.json template in current dir, see settings file
-update Update tracegl.js to the latest version, uses your token to fetch update
For other settings and commandline defaults traceGL supports a tracegl.json file which it tries to read from the current directory, your home dir, or the directory you store the tracegl.js file (in that order).
Create a template tracegl.json using the -settings command, and then modify these fields:
"ui":2000 Set the UI port, -ui:port commandline
"tgt":2080 Set the browser JS port, -tgt:port commandline
"no":[":match"] Takes an array, -no commandline options
"do":["/regexp"] Takes an array, -do commandline options
"theme" : "dark" UI Theme, other option: light
Editor integration uses a commandline call to your editor, and uses $file and $line to build up the arguments. Put it in the right platform key (darwin, win32, sunos, linux, freebsd). If you have a configuration thats useful, please consider sharing it in a github issue so it can be turned into a default.
"bin":"/Applications/Sublime Text 2.app/Contents/SharedSupport/bin/subl" "args":["$file:$line"]