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

douglas

v1.5.1

Published

Douglas fetches npm packages and installs them as ready-to-roll projects

Downloads

25

Readme

Hi, I'm Douglas.

I fetch npm packages and install them as ready to roll projects.

When I fetch an npm package, I empty it's contents to your current directory - along with all dependencies.

I'm perfect for seed projects, demos, and simple project scaffolding.

Install

Install me globally

npm i -g douglas

Now I'm on your command line.

Or if you just need me semi-frequently, you can just skip the global install and use via npx.

Let's find an npm package.

e.g...

If globally installed:

douglas get doug-test

Or if not installed globally...

npx douglas get doug-test

Douglas goes off an installs doug-test + dependencies, moves the contents to the current directory, and then removes doug-test from node_modules.

Publish

To publish a project, use


douglas publish

This clones your package.json and names it _package.json.

What's with the _package.json I hear you ask...

When douglas fetches a package - it replaces the package.json (that has been altered through the publishing process) with _package.json (which doesn't undergo any changes).

Fun fact: You can still douglas get any npm package, even if it doesn't have a _package.json, but you'll notice a far more verbose package.json due to all the the things that the npm publish process adds in.

Some tips when publishing

Remember to bump your version in package.json before publishing.

Also - make sure you include the keyword douglas to your package.json or even prepend your npm package with doug- or douglas- e.g. doug-test. Or douglas-test.

This just makes douglas packages easier to find.

When you're ready...


douglas publish