npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

node-builtin-map

v1.0.16

Published

Explicitly requires all built-in node modules and puts into a single object.

Readme

node-builtin-map

Explicitly requires all built-in node modules and puts into a single object.

You may think this is a very pointless module, and given the abundance of pointless modules on npm, I wouldn't blame you for thinking it. However, there is once very specific thing you can do with this module that requires the module to be in npm (otherwise, I would not have published it).

WZRD.IN

wzrd.in is a CDN that bundles node modules with browserify, for use in a normal web browser. This module requires the built-in node modules and provides them in a single object, meaning you can include the bundled version of this module in the browser and have access to the full node.js standard library.

Example

<!DOCTYPE html>
<html>
	<head>
		<script type="application/javascript" src="https://wzrd.in/bundle/node-builtin-map"></script>
		<script type="application/javascript">
			// This module includes a "require" function so that you can use the built-in modules just as if you were in nodejs
			require = require('node-builtin-map').require;
		</script>
		<script type="application/javascript">
			const os = require('os');
			console.log(os.platform()); // prints "browser"
		</script>
	</head>
	<body>
	</body>
</html>