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

acquire.js

v0.1.14

Published

Acquire application module. A build module encouragement tool as a step before your module becomes a full npm package.

Downloads

9

Readme

acquire.js

Require application module. A build module encouragement tool as a step before your module becomes a full npm package

Node is great and having functional units of code in modules that can be pulled in via require() is really nice. However, during the time when your application code is being built, accessing your lovely little modules isn't very clean, ex: var mymodule = require('./somepath/mymodule'). More importantly there's the overhead in setting up the repo, npm package, etc; when, you really need to get a project out the door. What if you could build you applicaton and then come back and then put all those nifty nuggets of functionality into formal packages and easily switch to code to using the newly packaged versions?

Enter acquire.js

Install

npm install acquire.js --save

Usage

Put your modules in the app_modules folder, in the same folder as your node_modules. Ex:

app_modules/
  nifty.js
  other/
    index.js
  profound/
    index.js
    package.json
    node_modules/
node_modules/

Then require('acquire.js') and use it to get your application module.

var acquire = require('acquire.js');
var mynifty = acquire('nifty') // nifty.js or nifty/index.js or as defined in nifty/package.json
var myother = acquire('other')

Later when you've packaged up your functionality and published it via npm publish and npm install nifty --save to add the package to your applcation. You simple change the call to acquire('nifty') to require('nifty')

var acquire = require('acquire.js');
var mynifty = acquire('nifty') // nifty is now a formal package
var myother = acquire('other')

Optional path

If you prefer another path for your application modules other than app_modules you can set it via the second parameter. Once passed, the default will remain changed until you change it again.

Example with your modules in other_path_modules:

other_path_modules/
  nifty.js
  other/
    index.js
  profound/
    index.js
    package.json
    node_modules/
node_modules/
var acquire = require('acquire.js');
var mynifty = acquire('nifty', 'other_path_modules') // change the default path on first use
var myother = acquire('other')

Bonus

If you want to easily access data in your bower.json, component.json, config.json or package.json files, you can simple acquire and then use them.

var acquire = require('acquire.js');
var myPack  = acquire('package')
console.log(myPack.name, myPack.version) // nifty 0.1.4

License MIT