blocks|key|1467576|text|答案很简单。No和No+(No)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467577|当javascript运行时，源文件/urls的概念已经不存在了。|1467578|也没有办法确定行号，因为在执行时，代码“行”的概念在Javascript中不再有意义。|1467579|特定的实现可以提供API挂钩，以允许特权代码出于调试目的而访问这些细节，但是这些API不会暴露于普通的标准Javascript代码。|1467580|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Answers are simple. No and No (No).

By the time javascript is running the concept of source files/urls from which the come is gone. 

There is also no way to determine a line number because again by the time of execution the notion of code "lines" is no longer meaningful in Javascript.

Specific implementations may provide API hooks to allow priviledged code access to such details for the purpose of debugging but these APIs are not exposed to ordinary standard Javascript code.

blocks|key|1467605|text|要确定某事物在哪一行上，您必须在所有代码中搜索占用感兴趣的特定行的代码，并从顶部到感兴趣的这一行计算"\n“字符，然后加1。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467606|我实际上是在我正在编写的应用程序中做这件事。它是一个用于HTML的最佳实践验证器，目前仍处于开发阶段，但您可能感兴趣的错误输出过程已经完成。|1467607|http://mailmarkup.org/htmlint/htmlint.html|offset|length|1467608|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|16|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

To determine which line something is on you have to search all the code for the code that occupies the particular line of interest and count the "\n" characters from the top to this of interest and add 1.

I am actually doing this very thing in an application I am writing. It is a best practices validator for HTML and is still heavily under development, but the error output process that you would be interested in is complete.

<a href="http://mailmarkup.org/htmlint/htmlint.html" rel="nofollow noreferrer">http://mailmarkup.org/htmlint/htmlint.html</a>

blocks|key|1252862|text|这通常是通过从当前上下文中抛出一个错误；然后分析error对象中的lineNumber和fileName+(某些浏览器具有)属性来实现的|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1252863|function+getErrorObject(){
++try+{+throw+Error('')+}+catch(err)+{+return+err;+}
}

var+err+=+getErrorObject();

err.fileName;
err.lineNumber;+//+or+`err.line`+in+WebKit|code-block|syntax|javascript|1252864|别忘了callee.caller属性已经被弃用了(而且在ECMA第3版中也从未真正出现过。首先)。|1252865|还要记住，函数反编译被指定为依赖于实现，因此可能会产生非常意想不到的结果。我在here和here上写过。|1252866|entityMap|0|LINK|mutability|MUTABLE|url|http://thinkweb2.com/projects/prototype/those-tricky-functions/|1|http://thinkweb2.com/projects/prototype/detecting-built-in-host-methods/^0|X|A|18|8|0|0|3|D|0|13|4|0|18|4|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]|$9|1B|A|1C|1|1D]]|E|$]]|$1|O|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]]]

This is often achieved by throwing an error from the current context; then analyzing error object for properties like <code>lineNumber</code> and <code>fileName</code> (which some browsers have)

<pre><code>function getErrorObject(){
 try { throw Error('') } catch(err) { return err; }
}

var err = getErrorObject();

err.fileName;
err.lineNumber; // or `err.line` in WebKit
</code></pre>

Don't forget that <code>callee.caller</code> property is deprecated (and was never really in ECMA 3rd ed. in the first place). 

Also remember that function decompilation is specified to be implementation dependent and so might yield quite unexpected results. I wrote about it <a href="http://thinkweb2.com/projects/prototype/those-tricky-functions/" rel="noreferrer">here</a> and <a href="http://thinkweb2.com/projects/prototype/detecting-built-in-host-methods/" rel="noreferrer">here</a>.

blocks|key|1467708|text|kangax的解决方案引入了不必要的try..catch作用域。如果你需要访问JavaScript中的行号(只要你使用的是火狐或Opera语言)，只需访问(new+Error).lineNumber即可。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1467709|entityMap^0|25|M|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

kangax's solution introduces unnecessary try..catch scope. If you need to access the line number of something in JavaScript (as long as you are using Firefox or Opera), just access <code>(new Error).lineNumber</code>.

blocks|key|1467730|text|这在chrome/QtWebView中适用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1467731|function+getErrorObject(){
++++try+{+throw+Error('')+}+catch(err)+{+return+err;+}
}

var+err+=+getErrorObject();
var+caller_line+=+err.stack.split("\n")[4];
var+index+=+caller_line.indexOf("at+");
var+clean+=+caller_line.slice(index%2B2,+caller_line.length);|code-block|syntax|javascript|1467732|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This works for me in chrome/QtWebView

<pre><code>function getErrorObject(){
 try { throw Error('') } catch(err) { return err; }
}

var err = getErrorObject();
var caller_line = err.stack.split("\n")[4];
var index = caller_line.indexOf("at ");
var clean = caller_line.slice(index+2, caller_line.length);
</code></pre>

blocks|key|1252987|text|看起来我来晚了:)，但是讨论很有趣，所以..开始了..。假设您想构建一个错误处理程序，并且您正在使用自己的异常处理程序类，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1252988|function++errorHandler(error){
++++this.errorMessage+=+error;
}
errorHandler.prototype.+displayErrors+=+function(){
++++throw+new+Error(this.errorMessage);
}|code-block|syntax|javascript|1252989|你可以这样包装你的代码：|1252990|try{
if(condition){
++++//whatever...
}else{
++++throw+new+errorHandler('Some+Error+Message');
}
}catch(e){
++++e.displayErrors();
}|1252991|您很可能将错误处理程序放在一个单独的.js文件中。|1252992|你会注意到，在火狐或chrome的错误控制台中，显示的代码行号(和文件名)是抛出'+error‘异常的行(文件)，而不是你真正想要的'errorHandler’异常，以便于调试。抛出自己的异常是很棒的，但在大型项目中定位它们可能是一个相当大的问题，特别是当它们有类似的消息时。因此，您可以做的是将一个对实际空错误对象的引用传递给您的错误处理程序，该引用将包含您需要的所有信息(例如，在firefox中，您可以获得文件名和行号等)。；在chrome中，如果你读取错误实例的'stack‘属性，你会得到类似的东西)。长话短说，你可以这样做：|1252993|function++errorHandler(error,+errorInstance){
++++this.errorMessage+=+error;
++++this.+errorInstance+=+errorInstance;
}
errorHandler.prototype.+displayErrors+=+function(){
++++//add+the+empty+error+trace+to+your+message
++++this.errorMessage+%2B=+'++stack+trace:+'%2B+this.+errorInstance.stack;
++++throw+new+Error(this.errorMessage);
}

try{
if(condition){
++++//whatever...
}else{
++++throw+new+errorHandler('Some+Error+Message',+new+Error());
}
}catch(e){
++++e.displayErrors();
}|1252994|现在，您可以获得抛出自定义异常的实际文件和行号。|1252995|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

It seems I'm kind of late :), but the discussion is pretty interesting so.. here it goes... Assuming you want to build a error handler, and you're using your own exception handler class like:

<pre><code>function errorHandler(error){
 this.errorMessage = error;
}
errorHandler.prototype. displayErrors = function(){
 throw new Error(this.errorMessage);
}
</code></pre>

And you're wrapping your code like this:

<pre><code>try{
if(condition){
 //whatever...
}else{
 throw new errorHandler('Some Error Message');
}
}catch(e){
 e.displayErrors();
}
</code></pre>

Most probably you'll have the error handler in a separate .js file.

You'll notice that in firefox or chrome's error console the code line number(and file name) showed is the line(file) that throws the 'Error' exception and not the 'errorHandler' exception wich you really want in order to make debugging easy. Throwing your own exceptions is great but on large projects locating them can be quite an issue, especially if they have similar messages. So, what you can do is to pass a reference to an actual empty Error object to your error handler, and that reference will hold all the information you want( for example in firefox you can get the file name, and line number etc.. ; in chrome you get something similar if you read the 'stack' property of the Error instance).
Long story short , you can do something like this:

<pre><code>function errorHandler(error, errorInstance){
 this.errorMessage = error;
 this. errorInstance = errorInstance;
}
errorHandler.prototype. displayErrors = function(){
 //add the empty error trace to your message
 this.errorMessage += ' stack trace: '+ this. errorInstance.stack;
 throw new Error(this.errorMessage);
}

try{
if(condition){
 //whatever...
}else{
 throw new errorHandler('Some Error Message', new Error());
}
}catch(e){
 e.displayErrors();
}
</code></pre>

Now you can get the actual file and line number that throwed you custom exception.

blocks|key|1253066|text|这是我根据在这个论坛上找到的信息写的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253067|这是MyDebugNamespace的一部分，Debug显然是保留的，不能用作命名空间名称。|1253068|++++var+DEBUG+=+true;|code-block|syntax|javascript|1253069|..。|1253070|++++if+(true+==+DEBUG+&&+!test)
++++{
++++++++var+sAlert+=+"Assertion+failed!+";
++++++++if+(null+!=+message)
++++++++++++sAlert+%2B=+"\n"+%2B+message;
++++++++if+(null+!=+err)
++++++++++++sAlert+%2B=+"\n"+%2B+"File:+"+%2B+err.fileName+%2B+"\n"+%2B+"Line:+"+%2B+err.lineNumber;
++++++++alert(sAlert);
++++}|1253071|1253072|如何调用：|1253073|++++MyDebugNamespace.Assert(new+Error(""),+(null+!=+someVar),+"Something+is+wrong!")|1253074|我在我的名称空间中包含了两个具有可变数量参数的函数来调用此基本代码，以便可以在调用中选择性地省略消息或错误。|1253075|这在火狐、IE6和Chrome上都能很好地工作，并将fileName和lineNumber报告为未定义。|1253076|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|10|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|M|3|J|5|6|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|13|8|@]|9|@]|A|$]]|$1|P|3|Q|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|R|3|S|5|6|7|15|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|16|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|W|$]]

Here is what I wrote based on info found on this forum:

This is part of a MyDebugNamespace, Debug is apparently reserved and won't do as namespace name.

<pre><code> var DEBUG = true;
</code></pre>

...

<pre><code> if (true == DEBUG &amp;&amp; !test)
 {
 var sAlert = "Assertion failed! ";
 if (null != message)
 sAlert += "\n" + message;
 if (null != err)
 sAlert += "\n" + "File: " + err.fileName + "\n" + "Line: " + err.lineNumber;
 alert(sAlert);
 }
</code></pre>

...

How to call:

<pre><code> MyDebugNamespace.Assert(new Error(""), (null != someVar), "Something is wrong!")
</code></pre>

I included two functions with variable number of arguments calling this base code in my namespace so as to optionally omit message or error in calls.

This works fine with Firefox, IE6 and Chrome report the fileName and lineNumber as undefined.

blocks|key|1253137|text|下面的代码可以在Mozilla和Chrome中运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253138|它的log函数显示文件名和调用者所在的行。|1253139|log:+function+(arg)+{
++++var+toPrint+=+[];
++++for+(var+i+=+0;+i+<+arguments.length;+%2B%2Bi)+{
++++++++toPrint.push(arguments[i]);
++++}

++++function+getErrorObject(){
++++++++try+{+throw+Error('')+}+catch(err)+{+return+err;+}
++++}

++++var+err+=+getErrorObject(),
++++++++caller;

++++if+($.browser.mozilla)+{
++++++++caller+=+err.stack.split("\n")[2];
++++}+else+{
++++++++caller+=+err.stack.split("\n")[4];
++++}

++++var+index+=+caller.indexOf('.js');

++++var+str+=+caller.substr(0,+index+%2B+3);
++++index+=+str.lastIndexOf('/');
++++str+=+str.substr(index+%2B+1,+str.length);

++++var+info+=+"\t\tFile:+"+%2B+str;

++++if+($.browser.mozilla)+{
++++++++str+=+caller;
++++}+else+{
++++++++index+=+caller.lastIndexOf(':');
++++++++str+=+caller.substr(0,+index);
++++}
++++index+=+str.lastIndexOf(':');
++++str+=+str.substr(index+%2B+1,+str.length);
++++info+%2B=+"+Line:+"+%2B+str;
++++toPrint.push(info);

++++console.log.apply(console,+toPrint);
}|code-block|syntax|javascript|1253140|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

the following code works for me in Mozilla and Chrome.

Its log function that shows the file's name and the line of the caller.

<pre><code>log: function (arg) {
 var toPrint = [];
 for (var i = 0; i &lt; arguments.length; ++i) {
 toPrint.push(arguments[i]);
 }

 function getErrorObject(){
 try { throw Error('') } catch(err) { return err; }
 }

 var err = getErrorObject(),
 caller;

 if ($.browser.mozilla) {
 caller = err.stack.split("\n")[2];
 } else {
 caller = err.stack.split("\n")[4];
 }

 var index = caller.indexOf('.js');

 var str = caller.substr(0, index + 3);
 index = str.lastIndexOf('/');
 str = str.substr(index + 1, str.length);

 var info = "\t\tFile: " + str;

 if ($.browser.mozilla) {
 str = caller;
 } else {
 index = caller.lastIndexOf(':');
 str = caller.substr(0, index);
 }
 index = str.lastIndexOf(':');
 str = str.substr(index + 1, str.length);
 info += " Line: " + str;
 toPrint.push(info);

 console.log.apply(console, toPrint);
}
</code></pre>

blocks|key|1253203|text|令我惊讶的是，这些答案中的大多数都假设您希望处理错误，而不仅仅是在正常情况下输出有用的调试跟踪。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253204|例如，我喜欢使用这样的console.log包装器：|offset|length|style|CODE|1253205|consoleLog+=+function(msg)+{//See+https://stackoverflow.com/a/27074218/470749
++++var+e+=+new+Error();
++++if+(!e.stack)+{
++++++++try+{
++++++++++++//+IE+requires+the+Error+to+actually+be+thrown+or+else+the+
++++++++++++//+Error's+'stack'+property+is+undefined.
++++++++++++throw+e;
++++++++}+catch+(e)+{
++++++++++++if+(!e.stack)+{
++++++++++++++++//return+0;+//+IE+<+10,+likely
++++++++++++}
++++++++}
++++}
++++var+stack+=+e.stack.toString().split(/\r\n%7C\n/);
++++if+(msg+===+'')+{
++++++++msg+=+'""';
++++}
++++console.log(msg,+'++++++++++['+%2B+stack[1]+%2B+']');++++++++
}|code-block|syntax|javascript|1253206|这最终会将如下输出输出到我的控制台：|1253207|1462567104174++++++++++[getAllPosts@http://me.com/helper.js:362:9]|1253208|请参阅https://stackoverflow.com/a/27074218/和A+proper+wrapper+for+console.log+with+correct+line+number?|1253209|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/27074218/|1|https://stackoverflow.com/questions/13815640/^0|0|B|B|0|0|0|0|1U|0|3|11|0|15|1M|1|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|16|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]|$D|1F|E|1G|1|1H]]|A|$]]|$1|S|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]]]

I was surprised that most of these answers assumed that you wanted to handle an error rather than just output helpful debug traces for normal cases as well.
For example, I like using a <code>console.log</code> wrapper like this:
<pre><code>consoleLog = function(msg) {//See https://stackoverflow.com/a/27074218/470749
 var e = new Error();
 if (!e.stack) {
 try {
 // IE requires the Error to actually be thrown or else the 
 // Error's 'stack' property is undefined.
 throw e;
 } catch (e) {
 if (!e.stack) {
 //return 0; // IE &lt; 10, likely
 }
 }
 }
 var stack = e.stack.toString().split(/\r\n|\n/);
 if (msg === '') {
 msg = '&quot;&quot;';
 }
 console.log(msg, ' [' + stack[1] + ']'); 
}
</code></pre>
This ends up printing an output such as the following to my console:
<code>1462567104174 [getAllPosts@http://me.com/helper.js:362:9]</code>
See <a href="https://stackoverflow.com/a/27074218/">https://stackoverflow.com/a/27074218/</a> and also <a href="https://stackoverflow.com/questions/13815640/">A proper wrapper for console.log with correct line number?</a>

blocks|key|1253297|text|行号实际上是静态的，所以如果你只是想用它来记录日志，那么它可以用类似gulp的东西进行预处理。我已经写了一个小的吞咽plugin，它就是这样做的：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1253298|var+gulp+=+require('gulp');
var+logLine+=+require('gulp-log-line');
gulp.task('log-line',+function()+{
++++return+gulp.src("file.js",+{buffer+:+true})
++++//Write+here+the+loggers+you+use.
++++++++.pipe(logLine(['console.log']))
++++++++.pipe(gulp.dest('./build'))

})

gulp.task('default',+['log-line'])|code-block|syntax|javascript|1253299|这会将文件名和行附加到来自console.log的所有日志，因此console.log(something)将变为console.log('filePath:fileNumber',+something)。优点是现在你可以连接你的文件，转换它们...你仍然会得到这条线|style|CODE|1253300|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/gulp-log-line^0|1M|6|0|0|0|W|M|1L|19|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@$A|10|B|11|K|L]|$A|12|B|13|K|L]]|9|@]|C|$]]|$1|M|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

Line number is actually something static, so if you just want it for logging then it could be preprocessed with something like gulp. I've written a small gulp <a href="https://www.npmjs.com/package/gulp-log-line" rel="nofollow">plugin</a> that does exactly that:

<pre><code>var gulp = require('gulp');
var logLine = require('gulp-log-line');
gulp.task('log-line', function() {
 return gulp.src("file.js", {buffer : true})
 //Write here the loggers you use.
 .pipe(logLine(['console.log']))
 .pipe(gulp.dest('./build'))

})

gulp.task('default', ['log-line'])
</code></pre>

This will attach the file name and line to all logs from console.log, so <code>console.log(something)</code> will become <code>console.log('filePath:fileNumber', something)</code>. The advantage is that now you can concat your files, transpile them... and you will still get the line

blocks|key|1468143|text|这就是我怎么做的，我已经在Firefox和Chrome上测试过了。这使得检查调用函数的位置的文件名和行号成为可能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468144|logFileAndLineNumber(new+Error());

function+logFileAndLineNumber(newErr)
{
+++if(navigator.userAgent.indexOf("Firefox")+!=+-1)
+++{
++++++var+originPath+=+newErr.stack.split('\n')[0].split("/");
++++++var+fileNameAndLineNumber+=+originPath[originPath.length+-+1].split(">")[0];
++++++console.log(fileNameAndLineNumber);
+++}else+if(navigator.userAgent.indexOf("Chrome")+!=+-1)
+++{
++++++var+originFile+=+newErr.stack.split('\n')[1].split('/');
++++++var+fileName+=+originFile[originFile.length+-+1].split(':')[0];
++++++var+lineNumber+=+originFile[originFile.length+-+1].split(':')[1];
++++++console.log(fileName%2B"+line+"%2BlineNumber);
++++}
}|code-block|syntax|javascript|1468145|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is how I have done it, I have tested it in both Firefox and Chrome. This makes it possible to check the filename and line number of the place where the function is called from.

<pre><code>logFileAndLineNumber(new Error());

function logFileAndLineNumber(newErr)
{
 if(navigator.userAgent.indexOf("Firefox") != -1)
 {
 var originPath = newErr.stack.split('\n')[0].split("/");
 var fileNameAndLineNumber = originPath[originPath.length - 1].split("&gt;")[0];
 console.log(fileNameAndLineNumber);
 }else if(navigator.userAgent.indexOf("Chrome") != -1)
 {
 var originFile = newErr.stack.split('\n')[1].split('/');
 var fileName = originFile[originFile.length - 1].split(':')[0];
 var lineNumber = originFile[originFile.length - 1].split(':')[1];
 console.log(fileName+" line "+lineNumber);
 }
}
</code></pre>

blocks|key|1253415|text|console.log(new+Error);|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1253416|它会向你展示整个赛道。|unstyled|1253417|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>console.log(new Error);
</code></pre>

It will show you the whole track.

blocks|key|1253479|text|我知道这是一个老问题，但现在有一个名为console.trace("Message")的方法，它将显示导致日志的行号和方法调用链以及您传递的消息。有关javascript日志记录技巧的更多信息，请参阅here+at+freecodecamp和this+medium+blog+post|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1253480|entityMap|0|LINK|mutability|MUTABLE|url|https://medium.freecodecamp.org/how-to-go-beyond-console-log-and-get-the-most-out-of-your-browsers-debugging-console-e185256a1115|1|https://medium.com/appsflyer/10-tips-for-javascript-debugging-like-a-pro-with-console-7140027eb5f6^0|J|O|2S|K|0|3D|L|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]|$9|V|A|W|1|X]]|E|$]]|$1|F|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]]]

I realize this is an old question but there is now a method called <code>console.trace("Message")</code> that will show you the line number and the chain of method calls that led to the log along with the message you pass it. More info on javascript logging tricks are available <a href="https://medium.freecodecamp.org/how-to-go-beyond-console-log-and-get-the-most-out-of-your-browsers-debugging-console-e185256a1115" rel="noreferrer">here at freecodecamp</a> and <a href="https://medium.com/appsflyer/10-tips-for-javascript-debugging-like-a-pro-with-console-7140027eb5f6" rel="noreferrer">this medium blog post</a>

I am using the following for getting the JavaScript caller function name:

<pre><code>var callerFunc = arguments.callee.caller.toString();
callerFuncName = (callerFunc.substring(callerFunc.indexOf("function") + 8, callerFunc.indexOf("(")) || "anoynmous")
</code></pre>

Is there a way to discover the line number from which the method was called?

Also, is there a way to get the name of the JavaScript file the method was called from? Or the source URL?

How to get JavaScript caller function line number and caller source URL

我使用以下代码来获取JavaScript调用方函数名：var callerFunc = arguments.callee.caller.toString();callerFuncName = (callerFunc.substring(callerFunc.indexOf("function") + 8, caller...

问如何获取JavaScript调用者函数行号和调用者来源URL
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何获取JavaScript调用者函数行号和调用者来源URLEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何获取JavaScript调用者函数行号和调用者来源URL
EN