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

urequ

v1.0.6

Published

Command line tool for finding correct require paths

Downloads

16

Readme

urequ

A simple cli command to know WTF is the correct path to be required when we have a complex project.

Install

npm install -g urequ

Usage

urequ requirer required

Find a library path

For example, imagine that inside

/Users/sullof/Projects/qabra/web/src/server/controller/jokes.es6

we want to require the library

/Users/sullof/Projects/qabra/common/lib/remote/funny.js

and we are in a terminal window at

/Users/sullof/Projects/qabra/web

Using the shell autocomplete we can easily execute

urequ src/server/controller/jokes.es6 ../common/lib/remote/funny.js

which will return

const funny = require('../../../../../common/lib/remote/funny')

If the requiring file is not a javascript file the result is a bit different. For example:

urequ src/server/controller/jokes.es6 src/server/data.json

will return

const dataJson = require('../data.json')

Inject a require statement

If you like, you can inject the line at the top of the requirer, specifying the name of the constant. For example:

urequ src/server/controller/jokes.es6 src/server/data.json Data

will inject at the top of jokes.es6 the line

const Data = require('../data.json')

If there is a statement 'use strict' the like is inserted after it. And, of course, after inserting it, you can move it where you like : )

MIT Licence

Version 1.0.0 — 02/25/2016

(c) Francesco Sullo [email protected]