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

lazreq

v0.1.1

Published

Lazy require / require on demand while keeping dependencies in module headers

Downloads

12

Readme

lazreq

Lazy require implementation

Goal

Load modules only when they are actually needed WHILE keeping dependencies listed on top of your files

Why

In a bigger project with a lot of modules or with big modules, initialization time may get increased if all modules get loaded and parsed before they are needed or even without them being needed at all (like conditionally used modules)

How to

Install

npm install lazreq

Use

JavaScript

var req = require('lazreq')({
  fs: 'fs',
  myLib: './lib/my-lib.js'
});

module.exports = function () {
  req.fs.exists('file_to_check.txt', function (exists) {
    if (exists) {
      req.myLib.amazingStuff();
    }
  });
}

CoffeeScript

req = require('lazreq')
  fs:    'fs'
  myLib: './lib/my-lib.js'

module.exports = ->
  req.fs.exists 'file_to_check.txt', (exists) ->
    if exists
      req.myLib.amazingStuff();

FAQ

How it works

It creates getters (using JavaScript standard standard Object.defineProperty methods) that will trigger loading modules on first read and return cached modules from the second read on

How do relative pathes work?

Just the way you would expect from require(): node_modules and pathes starting with './' or '../' will be looked up relative to the module file requiring them.