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

ral

v1.1.1

Published

Path aliasing for require.

Downloads

9

Readme

Require ALias Build Status

Require path aliasing.

This module allows you to easily move files and directories in your app without having to update many require calls. Instead you update the relevant alias definition.

The paths aliases to be used are defined in require-paths.json. All the paths are relative to the directory this file is in. To configure this directory you must set ral.basePath before your first usage of ral.

For example if require-paths.json is:

{
   "constants" : "lib/constants"
}

Then the base path can be set in the index.js at the root of the project using:

require('ral').basePath = __dirname;

Then the module at lib/constants can be retrieved with:

require('ral')('constants')

If the location of constants changes, only require-paths.json needs to be updated.

A path can be added after the key. For example given constants above:

require('ral')('constants/something')

will give you lib/constants/something.

Source (~20 lines)

TODO: test on windows

Release Notes:

  • 2014-06-02 0.0.1 Initial Release
  • 2014-06-03 0.1.0 Added tests & process.env.REQUIRE_PATHS
  • 2014-06-03 0.1.1 Locking down node version to >=0.8
  • 2014-06-04 0.1.2 Removing hard coded path separator
  • 2014-07-10 1.0.0 ral is dynamically configurable
  • 2014-10-01 1.1.0 the json object ral uses as its configuration can now be directly modified w ral.pathsConfig =
  • 2014-10-10 1.1.1 helpful errors if key is not found on require-paths