process information for node.js and browsers
Want to see pretty graphs? Log in now!
npm install process
|5 261||downloads in the last day|
|27 273||downloads in the last week|
|118 627||downloads in the last month|
|Last Published By|
|Version||0.6.0 last updated 3 months ago|
stream-browserify, generator-hazdev-weblib, global, serve-browserify, npm-proj, node-libs-browser, browserify-server, restoretty, siteboot, butterknife, joola.io.analytics, timers-ref, joola.io.config, raptor-optimizer-require, insert-module-globals, joola.io.engine, populate, mammock, introspect-reduce, cli-less,
and 16 more
|Starred by||luk, m42am|
require('process'); just like any other module.
Works in node.js and browsers via the browser.js shim provided with the module.
The goal of this module is not to be a full-fledged alternative to the builtin process module. This module mostly exists to provide the nextTick functionality and nothing more. We keep this module lean because it will often be included by default by tools like browserify when it detects a module has used the
If you are looking to provide other process methods, I suggest you monkey patch them onto the process global in your app. A list of user created patches is below.
package manager notes
If you are writing a bundler to package modules for client side use, make sure you use the
browser field hint in package.json.
See https://gist.github.com/4339901 for details.
The browserify module will properly handle this field when bundling your files.