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

lrequire

v1.0.5

Published

A module which allows you to require and try out npm modules directly without `npm install`-ing them. You can use this to quickly test out different modules in your project, inside a toy project or in the terminal.

Downloads

13

Readme

Live-require

NPM Build Status dependencies Code Climate

A module which allows you to require and try out npm modules directly without npm install-ing them. You can use this to quickly test out different modules in your project, inside a toy project or in the terminal.

How it works

Modules are downloaded and prepared in a predefined directory(/tmp/ by default) and then required back to you. The modules are cached so only the first time a module is used it might take a little longer to load.

Configuration

const lrequire = require('lrequire');

lrequire.configure({
    path: '/tmp/lrequire' //where the modules will be downloaded
})

Programmatic Usage

Basic:

const lrequire = require('lrequire');

const validUrl = lrequire('valid-url');
const latestVersion = lrequire('npmjs.org/package/latest-version');

Download specific version:

const lrequire = require('lrequire');

const validUrl = lrequire('valid-url', {
    version: '1.0.8'
});
const latestVersion = lrequire('npmjs.org/package/latest-version', {
    version: 'latest' //this is the default
});

You can also make lrequire global and use it at will. Later, if you wish to keep a package, you can remove the l and everything will continue working.

require('lrequire').global();

const validUrl = lrequire('valid-url');
const latestVersion = lrequire('npmjs.org/package/latest-version');

Repl Usage

Make sure to install lrequire globally:

$ npm i -g lrequire

Execute lrequire in your terminal, the lrequire function will be available in the newly opened repl which means you can directly start requiring modules. You can also use the require function, it will try to require a module and fallback to lrequire.

$ lrequire
> const { markdown } = require('markdown');
> $ markdown.toHTML('Hello *World*!');
'<p>Hello <em>World</em>!</p>'

What if you don't want to create files in your filesystem?

On linux consider using tmpfs. You can mount it on /tmp/lrequire or even /tmp which is a common practice. Don't forget that the directory where the files are saved can be configured.

On MacOS and Windows there are some RamDisk implementations that might work.

Requirements

Node 8

API Reference

lrequire(module, config = {version: 'latest'})

Require a module synchronously.

lrequire.async(module, config = {version: 'latest'}): Promise<Module>

Require a module asynchronously, the result can be awaited.

lrequire.asyncCallback(module, config, callback)

Require a module asynchronously, the result is passed as a second argument as per the node.js callback conventions.

lrequire.config(config = {path: '/tmp/lrequire'})

Configure lrequire.

lrequire.global()

Add lrequire to global.

lrequire.config

Get the config object

lrequire.latestVersionCache

Get the cache which holds the latest version available in npm for each package installed during the application's lifetime.