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

requirish

v0.3.0

Published

Tool for avoiding the ../../../ relative paths problem, includes browserify-transform to rewrites require() for browser

Downloads

1,687

Readme

#requirish

requirish is a tool for avoiding the ../../../ relative paths problem and includes a browserify-transform to rewrites the require() for browser.

You can use it both for your application and also if you are writing a library that could be referenced by others as dependency!

Installation

$ npm install --save requirish

Usage

In the code, before other require() calls:

require('requirish')._(module);
...

As a browserify-transform:

$ browserify -t requirish app.js > bundle.js

Example

Developing a not trivial Node.js application/library you will face a lot of annoying relative paths in your require() as soon as you start creating a module hierarchy under your ./lib source folder.

Your application, in this example, could have a 'jet.js' module like the following:

$ /Users/bob/my-app/lib/gui/controller/jet.js

and the relative unit-test with the following path:

$ /Users/bob/my-app/test/gui/controller/jet.test.js

Therefore, your 'jet.test.js' unit-test could begin like this:

var jetController = require('../../../lib/gui/controller/jet');
...

In such a case, browserify could resolve this long require() without any problem..

But, how to avoid using the ../../../ relative path to find the 'jet.js' module?

Well, you could write the require('requirish')._(module); statement - only one time for each module and before other require() - like the following:

require('requirish')._(module);

var jetController = require('lib/gui/controller/jet');
...

Fine! We will be happy to have now a path-decoupled require() but..
browserify will stop to resolve this new smart version!

And here requirish comes again to the rescue and transforms automagically all the smart require() in the previous ../../../ long version only for the browserify processor!

So, you could run the following browserify command adding the transform:

$ browserify -t requirish test/gui/controller/jet.test.js > test-bundle.js

Now, you will get a bundle that runs on browser without problem! :)

License

The project is released under the Mit License