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

npm-autoloader

v1.1.2

Published

Allows packages to specify modules to load on every run of npm.

Downloads

70

Readme

npm-autoloader

This provides extensible autoloading scripts to customize npm's behavior in the context of a given package – for example, to support alternative formats for the package.json file. This is a more flexible alternative to using npm's onload-script configuration variable.

Install

It's highly recommended to install npm-autoloader globally (either systemwide or somewhere else your $NODE_PATH will find it), due to the implementation of onload-script. You also need to set the onload-script config variable to point to the installation, though the config setting can be local instead of global.

npm install npm-autoloader --global
npm config set onload-script npm-autoloader --global

If you don't want to (or can't) install npm-autoloader globally, you can instead list the full, absolute path to the dist/index.js file:

npm install npm-autoloader
npm config set onload-script `node -e 'console.log(require.resolve("npm-autoloader"))'`

Use

npm-autoloader will look for one of the following files in your project root directory and/or your global configuration directory (whichever directory holds the npmrc file that you can edit with npm config edit --global):

  • npm-autoload.yaml
  • npm-autoload.yml
  • npm-autoload.json

This file should contain a list of autoload entries in either short or long format, containing the following options:

module (string, required) : the name of the module to load, in the same format expected by the require() function. Relative paths, which should start with . or .., as well as module resolution, behave as though the configuration file itself contained the require() statement.

func (string, optional) : the name of a function to call in the module. It will be passed an instance of the npm object, which can be queried for things like the command name. If the module exports a function called _npm_autoload, it will be used as a default when this is not specified.

required (boolean, optional) : whether this autoload entry must succeed for npm to be allowed to run. Ignored during initial npm install.

The short format is a string with the syntax [+]module[:func], where the required option is represented by a leading +.

During the initial npm install of a project (as determined by no existing node_modules/ directory and an npm install command line with no additional non-option arguments), npm-autoloader will silence any load errors from that project's npm-autoload.* configuration file and will not abort if the module was required, to allow for the initial dependency installation.

npm-autoload.yaml example

- package-yaml
- module: console
  func: log
  required: true
- +process:exit

npm-autoload.json example

[
    "package-yaml",
    {
        "module": "console",
        "func": "log",
        "required": true,
    },
    "+process:exit"
]

Environment variables

  • $DEBUG_NPM_AUTOLOADER - if present, output various debugging info.
  • $SKIP_NPM_AUTOLOADER - if present, do not do any autoload. Useful as SKIP_NPM_AUTOLOADER=1 npm install.