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

require-source-filepath

v1.0.1

Published

Finds the absolute filepath to the original sourcecode of any defined value

Downloads

3

Readme

require-source-filepath Build Status Coverage Status

Finds the absolute filepath to the original sourcecode that defines a value in node.

You may want to use this package if you're looking to do code introspection. When you import or require a file, it often isn't the file that actually defines the sourcecode for the variable you've just imported. This package lets you get the filepaths for the original source of your imported values.

Usage

$ npm install require-source-filepath 

const findSourcepath = require('require-source-filepath');
const { value1, value2 } = require('./values');
const { value3 } = require('values');

const paths = findSourcepath([value1, value2, value3]);

// paths = [
//   'path/to/original/sourcefile/of/value1',
//   'path/to/original/sourcefile/of/value2',
//   'path/to/original/sourcefile/of/value3',
// ]

How it works

require-source-filepath traverses node's global module variable recursively comparing exports from each export against the arguments. When it finds the deepest leaf node it returns the path of that file. It handles circular dependencies by traversing with a backtracking DFS.

Value types and Reference types

Due to its implementation and the data-structure of module , require-source-filepath may not always return the correct source file for any value types (number, string, bool etc.) and is not reccomended for their use.

If more than 2 files in the dependency tree export the same value type, require-source-filepath will return whichever file comes last in the dependency tree, regardless of whether it was the actual imported value or not.

require-source-filepath always returns the correct source file for all reference types (array's, function's, objects, classes, etc)