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 🙏

© 2026 – Pkg Stats / Ryan Hefner

sexy-require

v1.1.2

Published

No more ugly path inside require

Readme

💃🏻 Sexy require v 1.1

No more ugly path inside the require.

const user = require('../../../database/user') // 👎 what you have
// OR
const user = require('$db/user') // 👍 no matter how deep you are
const product = require('/database/product') // 👍 alias or pathing from application directory

Getting started

Three simple steps to use it.

  1. Install the package: npm install sexy-require --save

  2. Include require('sexy-require') once on the top of your main application file.

require('sexy-require')
const routers = require('/routers')
const api = require('$api')
...
  1. Optional step. Path configuration can be defined in .paths file on root directory of your project.
$db = /server/database
$api-v1 = /server/api/legacy
$api-v2 = /server/api/v2

List of paths

Anywhere in your project you can get the defined shortcut paths:

const path = require(`sexy-require`)
console.log(path.$db) // -> '/full/path/to/app/server/database'

Changelog

v 1.1

  • Seamless module require. If a given path doesn't exist in the app directory it will be ignored by sexy-require.

v 1.0

  • definition of path shortcuts moved from package.json to .paths config file
  • depending modules can use sexy-require too, previously it was not possible
  • supporting pathing from root directory, now it is not required to define shortcuts
  • caching and optimized code for higher performance

v 0.1

  • returns defined shortcut list with absolute path
  • minor bug fixes