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

js-resource-loader

v1.1.0

Published

Load clientside resources without CORS constraints and without polluting global scope.

Readme

js-resource-loader

This is a module that enables a convenient way to load external js resources dynamically and with scope. Instead of importing the contents of a script into the global scope, it loads the contents into an iframe and then extracts the contents a user specifically requests.

Note: this module was built to be loaded on the clientside with clientside-require;

npm install js-resource-loader --save

Example

Loading the google maps api without polluting your global scope:

(async function(){
    var load_resources = await load('js_resource_loader'); // the `load()` function is provided by `clientside-require`
    var google = await load_resources('https://maps.googleapis.com/maps/api/js?key=AIzaSyC_ymlgPnlMmPFzUFhJrRa0vivYGVGCSEE&libraries=places', "google");
})()

or equivalently

var promise_google = load('js_resource_loader')
    .then(load_resources=>{
        return load_resources('https://maps.googleapis.com/maps/api/js?key=AIzaSyC_ymlgPnlMmPFzUFhJrRa0vivYGVGCSEE&libraries=places', "google")
    })

Usage

load_resources(path, extraction_list, frame_src)

Path

Path is the url you would use in your browser to reach the resource manually. I.e., if you're not sure you have the right path, plug it into your url bar.

Extraction List

Extraction list is an array of key_strings which should be extracted from the environment the script is loaded into.

Note: if you only have one key you would like extracted, you can just pass the key string instead of an array.

Frame Src (optional)

If frame src is defined, then the iframe is loaded with the SRC as the contents. This may be useful when you need to load a script from a particular domain. (e.g., google looks for specific domains in which it authorizes the usage of certain api keys)