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-try-pkg

v1.0.1

Published

Quickly try npm packages without writing boilerplate code

Downloads

6

Readme

npm-try

🚆 Quickly try npm packages without writing boilerplate code.

asciicast

Build Status Commitizen friendly npm latest version

Install

$ npm install -g npm-try-pkg

Usage

npm-try provides a REPL interface for you to try NPM packages without writing any boilerplate code.

Simply run npm-try [packages ..] anywhere on the shell and npm-try will install the packages and show a REPL interface which has all packages required and assigned to variables.

Features

  • Super easy to use!
  • npm-try even defines variables for you
  • Top-level await support (requires Node.js >= 10)

Examples

Wanna try the capitalize method of lodash package?

$ npm-try lodash
✔ const lodash = require('lodash')
> lodash.capitalize('hello world')
'Hello world'

Would like to try multiple packages at the same time?

$ npm-try lodash underscore
✔ const lodash = require('lodash')
✔ const underscore = require('underscore')
> lodash.first([1, 2, 3])
1
> underscore.first([1, 2, 3])
1

A previous version? You can specify versions with @ symbol (Missing the old days when the pluck still exists).:

➜ npm-try lodash@3
✔ const lodash = require('lodash')
> lodash.pluck
[Function: pluck]

Asynchronous operations? await is supported out-of-the-box. Let's try ioredis:

$ npm-try ioredis
✔ const Redis = require('ioredis')
> const redis = new Redis()
undefined
> await redis.get('foo')
'123'

Create a Project

REPL is not enough sometimes when you want to write more code to test with packages. npm-try offers --out-dir/-o option to create a self-contained project so you can write your test code at the drop of a hat.

$ npm-try lodash -o try-lodash
✔ Installing lodash...
✔ The project created at /Users/luin/try-lodash

Limitations

Testing multiple versions of the same package is not supported. The following command will only have lodash@3 provided:

$ npm-try lodash@4 lodash@3
✔ const lodash = require('lodash')
✔ const lodash = require('lodash')
> lodash.VERSION
'3.10.1'

License

MIT