Package Exports

node-libs-browser
node-libs-browser/mock/buffer
node-libs-browser/mock/empty
node-libs-browser/mock/net
node-libs-browser/mock/tls
node-libs-browser/mock/tty

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (node-libs-browser) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

node-libs-browser

The node core libs for in-browser usage.

Exports a hash [object] of absolute paths to each lib, keyed by lib names. Modules without browser replacements are null.

Some modules have mocks in the mock directory. These are replacements with minimal functionality.

lib name	browser implementation	mock implementation
assert	defunctzombie/commonjs-assert	---
buffer	feross/buffer	buffer.js
child_process	---	---
cluster	---	---
console	Raynos/console-browserify	console.js
constants	juliangruber/constants-browserify	---
crypto	crypto-browserify/crypto-browserify	---
dgram	---	---
dns	---	dns.js
domain	bevry/domain-browser	---
events	Gozala/events	---
fs	---	---
http	substack/http-browserify	---
https	substack/https-browserify	---
module	---	---
net	---	net.js
os	CoderPuppy/os-browserify	---
path	substack/path-browserify	---
process	shtylman/node-process	process.js
punycode	bestiejs/punycode.js	---
querystring	mike-spainhower/querystring	---
readline	---	---
repl	---	---
stream	substack/stream-browserify	---
string_decoder	rvagg/string_decoder	---
sys	defunctzombie/node-util	---
timers	jryans/timers-browserify	---
tls	---	tls.js
tty	substack/tty-browserify	tty.js
url	defunctzombie/node-url	---
util	defunctzombie/node-util	---
vm	substack/vm-browserify	---
zlib	devongovett/browserify-zlib	---

Outdated versions

`buffer`

The current buffer implementation uses feross/buffer@4.x because feross/buffer@5.x relies on typed arrays. This will be dropped as soon as IE9 is not a typical browser target anymore.

`punycode`

The current punycode implementation uses bestiejs/punycode.js@1.x because bestiejs/punycode.js@2.x requires modern JS engines that understand const and let. It will be removed someday since it has already been deprecated from the node API.

`crypto`

We locked crypto-browserify at 3.3.0 because 3.4.x introduced a breaking change by requiring JSON files. We will not upgrade this module for webpack 1 anymore since it will introduce a breaking change for all users that don't have the json-loader configured. You can, however, use a newer crypto-browserify version by configuring a resolve.alias and using the json-loader.

License

MIT