Why does devtools show the wrong line number where console.log was called in a vue.js project?

Question

Google Chrome

Actually, the problem is that devtools somehow shifts the numbering when outputting to the console and stepping through the code. The project on vue.js, develop mode, source map are generated and everything seems to be fine there

console.log on line 328.
But in the console itself, devtools shows that the output was made from line 329.

If you insert a debugger into the code, then for debugging the cursor stops at the next line, and when stepping, it shifts by one line, that is, when passing the construction of the form

x=2;
  return x;
}

if the cursor is on return x, in fact, pressing F10 will execute the previous line, and the return from the function will be executed when F10 is pressed on the line with the closing bracket.
Whose problem is it - vue.js, webpack that generates the source map, or the devtools itself? Judging by the first screen, the maps are generated normally