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

myself

v1.0.1

Published

allows requiring of the current module by the name specified in the package.json

Downloads

7

Readme

node-myself

allows requiring of the current module by the name specified in the package.json

When developing a node.js package, you will often find it is a nightmare to refer to your package from within itself. You will often resort to code like:

const OurFramework = require('../../../index.js');

This package allows you to refer to your own package with the name you specified in the package.json file. For example:

const OurFramework = require('our-framework');

Usage is fairly simple, in your main file (index.js) you should simply add this line of code:

require('myself')(__dirname);

Documentation

The myself package exports a single function, that accepts a single argument:

require_me(string rootPath)

rootPath: The root folder of your project, this folder will be scanned for a package.json file and will be processed.

This function returns an object of the following format:

{
	RequireOverrideError: ..., // All errors inherit this class, this can be used for comparison
	Instance: ...              // The running instance of the require() interceptor
}

Instance

Once initialised, the interceptor provides a set of methods for handling updates:

setPath(string rootPath)

rootPath: The root folder of your project, this folder will be scanned for a package.json file and will be processed.

Updates the root path of the running instance. This will automatically trigger package redetection.

detectPackage()

Attempt to detect the package.json file in the root path. If found, the interceptor will be updated. If not found, an error will be thrown.