• Login
    • Report A Bug
    • System Information
    • System Tests
    • System Policies
    • Code Documentation
    • Occam Source Code
    • Web Client Source Code
    • About Occam
    • Acknowledgements
    • Guides / Documentation
    • Publications

translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
resource
  • git
    https://github.com/stefanpenner/get-caller-file.git Source Repository
    QmTMkBW41NNtUtfhj7tBuziC4vUoByUTqwWvmDNzqzv92v
    2383bf9e98ed3c568ff69d7586cf59c0f1dcb9d3
      QmTMkBW41NNtUtfhj7tBuziC4vUoByUTqwWvmDNzqzv92v
      2383bf9e98ed3c568ff69d7586cf59c0f1dcb9d3

      • Details
      • Files
      • History
        • Source

          https://github.com/stefanpenner/get-caller-file.git

          get-caller-file

          Build Status Build status

          This is a utility, which allows a function to figure out from which file it was invoked. It does so by inspecting v8's stack trace at the time it is invoked.

          Inspired by http://stackoverflow.com/questions/13227489

          note: this relies on Node/V8 specific APIs, as such other runtimes may not work

          Installation

          yarn add get-caller-file
          

          Usage

          Given:

          // ./foo.js
          const getCallerFile = require('get-caller-file');
          
          module.exports = function() {
            return getCallerFile(); // figures out who called it
          };
          
          // index.js
          const foo = require('./foo');
          
          foo() // => /full/path/to/this/file/index.js
          

          Options:

          • getCallerFile(position = 2): where position is stack frame whos fileName we want.

          Related

          • maintainer

            npm

          Share

          • URL

            Copy
          • Embed Link

            Copy
          • QR Code

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        Confirm
        Do you wish to proceed?

        Confirm message?