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

grunt-global-wrap

v1.1.0

Published

Grunt task to expose your CommonJS-based libraries as a global.

Downloads

14

Readme

Global-ify Your CommonJS, via Grunt

This is a Grunt plugin to expose your CommonJS libraries as globals on window. It allows you to produce build artifiacts that are readily usable by people who haven't embraced the magnificence of browserify. You point it at your main module, and it exposes that as a specified property of the global, bundling up everything it requires (including any native module shims) into the output file.

It's based on global-wrap, if you want this functionality outside of a Grunt plugin.

Usage

It takes four options, three of which are required:

  • main: the file path of your main module, which you want to expose as a global.
  • global: the name of the global you want to expose.
  • dest: the place where your new global-exposing file should be written.
  • bundleOptions: any browserify bundle options you want to pass along, like debug or detectGlobals. This is the optional option.

Here's a quick sample:

grunt.loadNpmTasks("grunt-global-wrap");

grunt.initConfig({
    globalwrap: {
        releaseArtifactsTarget: {
            main: "my-main-module.js",
            global: "myModule",
            dest: "release/my-module.global.js",
            bundleOptions: { debug: true }
        }
    }
});