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

@jsumners/require-self-ref

v3.0.1

Published

Solves the relative path problem in Node.js by allowing a require call to reference the current package

Downloads

5

Readme

@jsumners/require-self-ref

Fork Notice: this is a fork of the original require-self-ref. This fork removes production dependencies so that it is a fully self-contained module. Any issues with this fork should not be directed at the upstream project.

Solves the relative path problem in Node.js by allowing the target module argument of a require call to be relative to the root directory of the containing package:

For example:

Given a JavaScript module at my-package/src/some/deeply/nested/path/foo/index.js that needs to require my-package/src/util/bar.js:

Without require-self-ref:

require('../../../../../../util/bar')

:confused:

And with require-self-ref installed:

require('~/src/util/bar')

:smile:

Installation

npm install @jsumners/require-self-ref

Usage

At the top of the main entry for your application add the following line:

require('@jsumners/require-self-ref')

Important

  • Your package must have a package.json file at the root
  • Use at your own risk (this package monkey-patches the Node.js require system and it depends on internals of Node.js that may change in the future)
  • Compatible with all versions of Node.js

Related projects:

  • app-module-path - Simple module to add additional directories to the Node module search for top-level app modules
  • wavy - Similar to this package, but requires a postinstall script and symbolic links

License

MIT