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

umd-free-zone

v0.1.3

Published

Creates a define and exports free zone for your UMD scripts to safely register globally

Downloads

23,352

Readme

umd-free-zone

umd-free-zone is meant to prevent your UMD-compatible scripts from falling for unwanted global AMD and CommonJS shims.

Just add umd-free-zone/start.js before your scripts and umd-free-zone/end.js after them.

This will ensure your scripts register globally.

Example

Imagine you want to load the UMD compatible React from unpkg and intend for it to become a global (window.React).

Yet, you have an evil Mailchimp script that brutally exports a global define function, and you can't guarantee your React will load before the nasty AMD leak.

umd-free-zone to the rescue! Just add it before and after the scripts you want to become global.

Bad:

React will fall for the alien global define.

// Nasty script that globally defines a `define` function
<script src="https://downloads.mailchimp.com/js/signup-forms/popup/embed.js"></script>

<script src="https://unpkg.com/[email protected]/umd/react.production.min.js"></script>
<script> window.React // undefined! Ouch. </script>

Good:

Wrap your scripts in umd-free-zone start and end:

// Nasty script that globally defines a `define` function
<script src="https://downloads.mailchimp.com/js/signup-forms/popup/embed.js"></script>

<script src="https://unpkg.com/[email protected]/start.js"></script>
<script src="https://unpkg.com/[email protected]/umd/react.production.min.js"></script>
<script> window.React // undefined! Ouch. </script>
<script src="https://unpkg.com/[email protected]/end.js"></script>

// The leaky AMD works as usual from here onwards, if you want it to.