ChatGPT解决这个技术问题 Extra ChatGPT

How do you find out the caller function in JavaScript when use strict is enabled?

Is it possible to see the callee/caller of a function when use strict is enabled?

'use strict'; function jamie (){ console.info(arguments.callee.caller.name); //this will output the below error //uncaught TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed on strict mode functions or the arguments objects for calls to them }; function jiminyCricket (){ jamie(); } jiminyCricket ();

In general (with very few exceptions) if you want to do that - you are doing something wrong. Try to explain the real problem you want to solve wit this code.
There is no alternative. The recommended way is to use the function name directly like jamie.name // jamie. But function names are often irrelevant, other than for debugging, they make no difference in your code, and relying on this functionality for something other than recursion is usually an XY problem.
To be honest, there isn't any real problem with my code, but I have a function aliasing console.info so c = console.info essentially. So when I console something with said function, it just shows in the console that it came from the same place every time. i wanted to output which function called it. Just for my being lazy and cool all rolled into one :D
ye of course :) But that means pressing f11.... I don't wanna have to do anything more if a little bit of code could do this for me :p I'm a programmer.. Its the only reason I do this... I'm lazy
This MDN document gives an explanation why it was removed from JS Strict Mode. Basically, the ability to use arguments.callee and arguments.caller made certain JS engine optimisations difficult/impossible.

T
Tieme

For what it's worth, I agree with the comments above. For whatever problem you're trying to solve, there are usually better solutions.

However, just for illustrative purposes, here's one (very ugly) solution:

'use strict'

function jamie (){
    var callerName;
    try { throw new Error(); }
    catch (e) { 
        var re = /(\w+)@|at (\w+) \(/g, st = e.stack, m;
        re.exec(st), m = re.exec(st);
        callerName = m[1] || m[2];
    }
    console.log(callerName);
};

function jiminyCricket (){
   jamie();
}

jiminyCricket(); // jiminyCricket

I've only tested this in Chrome, Firefox, and IE11, so your mileage may vary.


ha great idea. Throw a error. It really isn't a big deal as such. Just would be nice to know where the console.log's are coming from. I don't see this as a problem?
This worked well. We had to use the throw version instead of @inetphantom's solution because an embedded JavaScript engine we had to work with didn't populate Error().stack until it was thrown.
Hi, is there any way to get parameters of the caller function?
you got an upvote because the ugliness yet cleverness made me laugh
I don't think you have to throw the error, it should be enough just to run that regex on new Error().stack
M
Manav Kataria

Please note that this should not be used in production. This is an ugly solution, which can be helpful for debugging, but if you need something from the caller, pass it as argument or save it into a accessible variable.

The short version of @p.s.w.g answer(without throwing an error, just instantiating one):

    let re = /([^(]+)@|at ([^(]+) \(/g;
    let aRegexResult = re.exec(new Error().stack);
    sCallerName = aRegexResult[1] || aRegexResult[2];

Full Snippet:

'use strict' function jamie (){ var sCallerName; { let re = /([^(]+)@|at ([^(]+) \(/g; let aRegexResult = re.exec(new Error().stack); sCallerName = aRegexResult[1] || aRegexResult[2]; } console.log(sCallerName); }; function jiminyCricket(){ jamie(); }; jiminyCricket(); // jiminyCricket


The regex to match the name in the stack should probably be ([^(]+) instead of (\w+) because spaces and punctuation are common.
You added a warning for production use... Hmmm... The function is not pure, indeed. But should that be a serious reason for not using it in production code? The code seems to be pretty stable (as far as I can judge). And a very interesting application would be in a logging method. In that case, passing the caller name in a parameter would be tedious, bloating and error-prone. So, as I see it, the decision of why and when certain code should be used in production or not mainly depends on the software design and some common sense. I will gladly use it in production code if it works for me.
Ah. I see now. The Error.prototype.stack property is officially marked as non-standard and implementation-specific.
From the Error.prototype.stack documentation on MDN: "Different browsers set this value at different times. For example, Firefox sets it when creating an Error object, while PhantomJS sets it only when throwing the Error, and archived MSDN docs also seem to match the PhantomJS implementation." So p.s.w.g's answer (involving creating, throwing and catching an Error) might be more robust anyway...
@BartHofland I still wouldn't use it - Where is the point of logging who called a function? If there is an error - log that error.
B
Benamar

It does not worked for me Here is what I finally do, just in case it helps someone

function callerName() {
  try {
    throw new Error();
  }
  catch (e) {
    try {
      return e.stack.split('at ')[3].split(' ')[0];
    } catch (e) {
      return '';
    }
  }

}
function currentFunction(){
  let whoCallMe = callerName();
  console.log(whoCallMe);
}

Cany ou please explain why this worked for you and the other solutions did not?
I had something like exception on aRegexResult[1] index out of range
aregexResult[1] index out of range is because names in the call stack that don't match \w+ are skipped. You should use [^(]+ instead.
This solution should work much faster than Regex.
This seems to work the best for an Angular/TypeScript configuration.
L
Larry

You can get a stack trace using:

console.trace()

but this is likely not useful if you need to do something with the caller.

See https://developer.mozilla.org/en-US/docs/Web/API/Console/trace


t
toddmo
  functionName() {
    return new Error().stack.match(/ at (\S+)/g)[1].get(/ at (.+)/);
  }

  // Get - extract regex
  String.prototype.get = function(pattern, defaultValue = "") {
    if(pattern.test(this)) {
      var match = this.match(pattern);
      return match[1] || match[0];
    }
    return defaultValue; // if nothing is found, the answer is known, so it's not null
  }