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

loaddotjs

v1.0.3

Published

Javascript bundler & code-splitter in the browser #microstack

Downloads

14

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

coderofsalvationcoderofsalvation

Keywords

Readme

Javascript bundler & code-splitter in the browser #microstack

Usage

    <html lang="en">
      <head>
        <script src="load.js"></script>
      </head>
      <body>
        <div id="app"></div>
        <script>
            load([
                "http://stylus-lang.com/try/stylus.min.js",
                "https://unpkg.com/[email protected]/dist/vue.min.js",
                "https://unpkg.com/[email protected]/dist/vue-router.js",
                "https://unpkg.com/[email protected]/src/httpVueLoader.js",
                "https://unpkg.com/[email protected]/dist/default-skin/default-skin.css",
            ],'/js/bundle.js') 
            .then( () => load(["/js/main.js"]) ) 
            .catch( console.error )
        </script>
      </body>
    </html>

Now loading index.html will work as usual. Loading index.html?dev, will trigger the bundler (or type load.cmd('dev') in the devtools console).

The second argument (/js/bundle.js hints loadjs that it can be bundled, resulting in a tab on the right). Loading the html-file without the ?flag (or running load.cmd('')) will load the bundled-version instead of the individual files.

Install

Just save load.js to a directory, or run this in the terminal:

$ wget https://raw.githubusercontent.com/coderofsalvation/load.js/master/load.js

And add index.html like shown above

Extending

Developers can add tabs to trigger other tools, tests or actions like so:

load.addButton('my tab', () => alert('run test') )

Why

The time is ripe for in-browser webdevelopment:

  • es6 is supported in current browsers
  • chrome devtools allows serving gitrepositories locally using 'overrides'
  • javascript modules work in the browser
  • sass-like css syntax can run directly in the browser using stylus .e.g
  • code-splitting can be achieved using http-vue-loader and similar module-loaders
  • npm modules can be included directly in the browser using npm CDN's like unpkg.com
  • api responses can be easily mocked or requested remotely

It goes without saying that this doesn't apply for people who got emotionally or financially attached to their current tools & stacks.

How to develop locally?

Simple create an Overrides-directory with projects, for example on a chrome book

hit ctrl-t to start a terminal
> shell 
$ cd Downloads
$ mkdir Overrides
$ cd Overrides
$ mkdir myproject.com

Now add 'Overrides' as the overrides folder, and type https://myproject.com and voila..a free IDE editor + it serves the webpage over https!