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

autoload

v0.1.2

Published

Autoloading symbols via source code grokking

Downloads

1,600

Readme

autoload -- Automatically load symbols in NodeJS

INTRODUCTION

In NodeJS, and CommonJS in general, it's difficult to depend on common globals to be defined when you need them. This has led to very chatty or verbose boilerplate in applications to grab handles to functions and objects in every module in a project.

Generally module exports are used to define pseudo-classes or pseudo-namespaces which make sense as as globals. The problem is that even if your module defines its exports as global there's no way to be sure the module you depend on has been required or not. autoload attempts to ease this situation.

INSTALLING

	npm install autoload

GETTING STARTED

In your top-level script, call autoload and registeredGlobalsAutoloader to initialize a typical autoloading environment:

	main.js:
	var autoload = require('autoload');
	autoload.autoload(__dirname, [autoload.registeredGlobalsAutoloader(require)], function() {
		<< your regular code goes here >>
	});
	<< don't put code here, as autoload is not ready yet! >>

To register a global as autoloadable, in another module you would do:

	my-global-function.js:
	registerGlobal(function MyGlobalFunction() {
		<< function here >>
	});

When you call autoload it will search __dirname for Javascript files and attempt to find all globals which could be defined (via registerGlobal). After it finds those symbols it registers autoloading getters on the global object (but does not actually require the module). When the getter is invoked the module is require'd and the symbol is returned.

Be sure to look at the source code for registeredGlobalsAutoloader, as you can use this library to autoload symbols in scopes outside of global as well, or you can implement your own global exporting pattern too. For instance of you prefer global.MySymbol = ... or MySymbol = ... you could wire that up. I prefer having the global be super explicit which is why I made registerGlobal().