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

intern-requirements

v0.0.6

Published

node.js internal dependencies manager. Require files the easy way

Downloads

11

Readme

node-internRequirements

internal requirements manager. Require internal files the easy way!

Install via npm

npm install intern-requirements

Usage

First you need a dependencies.json file on the working directory of the node process.

{
  "foo" : "modules/foo.js",
  "bar" : "modules/bar/index.json"
}

In this example we registered two internal dependencies. Foo with the file path modules/foo.js and barwith modules/bar/index.json. These path definitions are relative current working directory. (process.cwd())

After that you can require the internal modules via

require("intern-requirements")("Foo")

Alternative dependencies.json location

By default inter-requirements expects the dependencies.json file in the current working directory. If you need to execute your code from another directory you can define a relative path starting from the current working directory to your custom dependencies.jsonfile by defining the environment variable REL_DEP_LOC. For example:

REL_DEP_LOC="src" node src/main.js

Environment Settings

If you need to, you can define modules depending on the NODE_ENV. Just define a ENV Object inside of your dependency.json

{
  "foo" : "modules/foo.js",
  "bar" : "modules/bar/index.json",
  "ENV" : {
    "test" : {
      "foo" : "modules/foo-dev.js"
    }
  }
}

Require node modules

You can require node modules as an alternative to the file requirement.

{
  "mocha" : {
    "require": "mocha"
  },
  "mochaRunner" : {
    "require": "mocha/lib/runner"
  }
}

Changelog

0.0.6

  • add require module functionality

License

Unless stated elsewhere, file headers or otherwise, the license as stated in the LICENSE file.