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

module-parent-id

v0.1.0

Published

Get the ID (filename) of module parent.

Downloads

10

Readme

Module Parent ID

Get ID of module parent

Useful when you want to get the ID (filename) of module parent.

Install

$ npm install module-parent-id --save

Know more

Assume that we have two nested modules into /home/hastijs directory. That means we require module two into module one.

/home/hastijs/
|_ module-one.js
   |_ module-two.js

Now we run module-one while module-parent-id called into module-two.

// module-tow.js
console.log(require('module-parent-id')());

The result is:

//=> /home/hastijs/module-one.js

Usage

In example bellow, module-one executed.

Get module immediate parent ID

// module-two.js (path: /home/hastijs/module-two.js)
const moduleParentId = require('module-parent-id');
console.log(moduleParentId());
// module-one.js (path: /home/hastijs/module-one.js)
require('./module-two');
//=> /home/hastijs/module-one.js

Get module upper parent ID

// module-three.js (path: /home/hastijs/module-three.js)
const moduleParentId = require('module-parent-id');
console.log(moduleParentId(2));
// module-two.js (path: /home/hastijs/module-two.js)
require('./module-three');
// module-one.js (path: /home/hastijs/module-one.js)
require('./module-two');
//=> /home/hastijs/module-one.js

API

moduleParentId(upLevel)

upLevel

Type: number

Default: 1

Number of upper parent.

Contributing

Everyone is very welcome to contribute to Module Parent ID project. Module Parent ID is a HastiJS project so please see HastiJS contributing guidelines before contributing.

License

MIT © HastiJS