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

be-goods

v0.0.9

Published

let there be beverage goods

Downloads

1,000

Readme

be-goods -- gulp beverage goods version npm

NPM

Utility exports for beverage / gulp / workflow helpers. About half of the exports are rather generic. Especially prefquire which is a require that prefers local modules. It takes some options and returns a customized "require" function. Perhaps it would be worthwhile to extract it into its own repository / packaged module... It needs a few of the other be-goods exports though, which in turn are used by some of the other beverage modules, so perhaps it's just a bit of a "who cares"? It kind of enables peer-dependencies making a library lighter. It also gives one better control over the versions of modules being required. This is convenient for modules getting new features more independently and allows having more granular control of upgrades. For example:

var req = require('be-goods').prefquire({module: 'try-here-too'})
var aModule = req('a-module')

Trying to require a-module from:

  1. ./node_modules/a-module
  2. ./node_modules/try-here-too/node_modules/a-module

The path to try-here-too can be anywhere you please, by calling for example prefquire({locate: 'anywhere/try-here-too'}). There are a few more options available, see the source code for details.

Develop Dependency Status devDependency Status

gulp dev

js-standard-style

License

MIT