process - npm Package Compare versions

process

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Comparing version 0.11.1 to 0.11.2

browser.js

		@@ -33,3 +33,5 @@ // shim for using process in browser
		while (++queueIndex < len) {
		currentQueue[queueIndex].run();
		if (currentQueue) {
		currentQueue[queueIndex].run();
		}
		}
		@@ -86,3 +88,2 @@ queueIndex = -1;

		// TODO(shtylman)
		process.cwd = function () { return '/' };
		@@ -89,0 +90,0 @@ process.chdir = function (dir) {

package.json

README.md

		@@ -9,4 +9,6 @@ # process

		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 `process` global.
		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 little 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 `process` global.

		It also exposes a "browser" member (i.e. `process.browser`) which is `true` in this implementation but `undefined` in node. This can be used in isomorphic code that adjusts it's behavior depending on which environment it's running in.

		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.
		@@ -13,0 +15,0 @@

Fixed alerts