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

calling-file

v1.0.0

Published

Get the file or directory name of the file that called you

Downloads

7

Readme

Calling File

Sometimes you want to know the path (or directory) of the file that called the function you are in. Calling file makes use of callsites to provide that path.

Installation

$ npm install calling-file

Use

// ./a.js
const callingFile = require('calling-file');

module.exports = () => {
	console.log(callingFile());
}
// ./b.js
const a = require('./a.js');

a(); // '/Users/someone/project/b.js'

These files are provided in example directory. You can run node example/b.js and get it's full path.

$ node example/b.js
/Users/someone/projects/node/calling-file/example/b.js

callingFile([options])

options

dir

Type: boolean

Indicates that the directory of the calling file should be returned rather than the calling file itself. This can be useful in conjunction with resolve-from and other APIs that expect a directory.

Note: setting the dir flag does not effect how file paths are matched in any way. The directory of the calling file path is calculated after the calling file has been determined.

ignore

Type: Array of file paths

Indicates that the listed paths should be ignored when determining the calling path. This can be useful when you know certain modules in the call stack but want to know the file that called them.

Similar Modules

  • caller-callsite - Sindre Sorhus's implementation of a similar feature
  • parent-module - one potential use of a module like this, again by Sindre Sorhus
  • intercept-require - has some similar code embedded in it for determining which file is calling require()

License

Copyright (c) 2017 Aaron Madsen

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.