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

load

v1.0.2

Published

Load plain JavaScript files that don't use module patterns directly in node.

Downloads

4,610

Readme

load

Build Status NPM version

Because fuck dedicated module patterns, module loaders, compilers and other kind of pointless code bloat that requires me to wrap my client-side JavaScript for server usage.

People need to understand that the Node.js module system is nothing more then a vm that reads our a pre-defined module variable. We don't need to be stuck in this pattern, we can just get all the globals that are introduced while we load the script and tada, we're running the snippet on the server.

Installation

Load is available in npm so you can install it by running:

npm --save load

API

var load = require('load');

// file.js contents:
//
// function test() { return 'test' };
//

// load returns all the introduced globals as an object, so specify the name of
// function you need in order to call it.
var test = load('file.js').test;

// file2.js contents:
//
// function test() {}
// function test1() {}
//

var library = load('file2');
console.log(library.test);
console.log(library.test1);

var moo = load.compiler('function cow() { console.log("moo") }', 'moo.js');
moo(); // console.log('moo');

// And that it.

License

MIT