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 🙏

© 2024 – Pkg Stats / Ryan Hefner

bowrap

v1.0.6

Published

A very simple browser support wrapper for allowing import of node modules in the browser.

Downloads

10

Readme

bowrap

A very simple and small browser support wrapper to make node modules available in the browser.

Install

npm install bowrap -g

Usage

In your package.json

  :
  :
  "scripts": {
    "test": "mocha --compilers js:babel-register",
    "build": "npm run babel && npm run bowrap && npm run uglify",
    "babel": "babel --presets es2015 index.js --out-file .tmp/es5.js",
    "bowrap": "bowrap es5.tmp -o bowrapped.tmp -n myLib",
    "uglify": "uglifyjs bowrapped.tmp --output dist/index.min.js --screw-ie8 --compress",
    "clean": "del-cli *.tmp"
  },
  :
  :

Output

Your module will be importable by node's require, ES6 import and can be added as browser script; useful if you want to package for bower.

So if you were importing your module in ES6 using:

import myLib from 'my-lib';
myLib.doStuff();

After being bowrapped your module would also be available for people directly importing your script:

myLib.doStuff();

Note

For the package name, bowrap uses the name field in package.json in the current project unless specified with -n or --name.

What actully happened to my code?

Not that much really. Bowrap wraps your module in a self calling function and puts export and module objects on the global window object if it exists. After the module exports bowrap will make it available on the global window object. See the test folder for an example.