Process tracing and flame graph visualization tool for Node.js development
A process tracing and flame graph tool for node.js development
On Mac:
echo "$(whoami) ALL=(ALL) NOPASSWD: /usr/sbin/dtrace" | sudo tee -a /etc/sudoers
On Linux:
echo "kernel.perf_event_paranoid=-1" | sudo tee -a /etc/sysctl.conf > /dev/null
sysctl -p
npm install --save-dev infernode
in your Node.JS NPM projectnpx infernode
to launch INFERNOdesrc/index.js
)npm install
in the repo directorynpm run dev
to run the server with on-save recompile/reloadAll scripts are accessible via npm run <scriptname>
, some key scripts are:
resetdb
: Clean out infernode's datastore for a fresh startclean
: Remove all contents of the ./dist/
directorycopy-assets
: Copy static assets from ./src/
to ./dist/
lint
: Run linter (ESLint) against the relevant client and server source codebuild
: Performs npm run prebuild
, npm run tsc
, and npm run webpack
sequentially, will halt if any prebuild
steps have non-zero exit codestest
: Performs a fresh build
and then executes all test suitesstart
: Starts the node
server in production mode, access via http://localhost:3000
dev
: Starts the node
and webpack-dev-server
servers in development mode, both dynamically recompiling/bundling/restarting on source code changes, access via http://localhost:8080
next( errObject: InfernodeError )
.InfernodeError
type object with the following mandatory properties:
message: string
: A technical error message not necessarily intended for end usersInfernodeError
object can optionally include:
userMessage: string
: A non-technical error message intended for (public) end users or API consumershttpStatus: number
: A more specific HTTP status code to use for the responsecontroller: string
: The Express middleware controller/function/method/operation that caused the errorerrObject.httpStatus
code is not provided.Please see CONTRIBUTING.md for standards and process related to contributing to this project.