How to understand where the error at build time webpack?

Added to the old project Vuetify. In development mode Belitsa (but the size is under 8Mb comes out). I want to see how it will compress and try to sbility to prod, config with ineficacia. Build passes, but in the end crashes with the error. And, already, it seems, afteractually build:
 | ./lumen/src/app/videoCategories.js 1.24 KiB [depth 13] [built]
 | [exports: default]
 | [all exports used]
 | harmony side effect evaluation App/videoCategories ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib??vue-loader-options!./lumen/src/components/TovidioOverlayDetails.vue?vue&type=script&lang=js& 50:0-57
 | harmony specifier import App/videoCategories ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib??vue-loader-options!./lumen/src/components/TovidioOverlayDetails.vue?vue&type=script&lang=js& 143:4-26
 | + 120 hidden modules
 + 165 hidden modules

LOG from webpack.buildChunkGraph.visitModules
<t> prepare: 46.1219 ms
<t> visiting: 3.6636 ms

ERROR in unknown: Unexpected token (19114:11)
npm ERR! errno 2
npm ERR! myproject@1.0.0 build: `webpack --verbose --config`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the myproject@1.0.0 a build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-01-05T10_05_57_122Z-debug.log

Config webpack'and divided into two branches. In addition to the General webpack.common.js there and
const merge = require('webpack-merge');
const common = require('./webpack.common.js');
const MinifyPlugin = require("babel-minify-webpack-plugin");

module.exports = merge(common, {

 mode: 'production',
 devtool: 'source-map',
 plugins: [
 new MinifyPlugin(),

What could be the cause of the error, and how to find out exactly where it occurs — in which file the string 19114?

In womancom the log file contains nothing useful:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node' '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm@6.13.4
3 info using node@v13.5.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle myproject@1.0.0~prebuild: myproject@1.0.0
6 info lifecycle myproject@1.0.0~build: myproject@1.0.0
7 verbose lifecycle myproject@1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle myproject@1.0.0~build: - PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle myproject@1.0.0~build: CWD: /usr/src/app
10 silly lifecycle myproject@1.0.0~build: Args: [ '-c', 'webpack --config' ]
11 silly lifecycle myproject@1.0.0~build: Returned: code: 2, signal: null
12 info lifecycle myproject@1.0.0~build: Failed to exec build script
13 verbose stack Error: myproject@1.0.0 build: `webpack --config`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:305:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:305:20)
13 verbose stack at maybeClose (internal/child_process.js:1028:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid myproject@1.0.0
15 verbose cwd /usr/src/app
16 verbose Linux 4.9.184-linuxkit
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v13.5.0
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 2
22 error myproject@1.0.0 build: `webpack --config`
22 error Exit status 2
23 error Failed at the myproject@1.0.0 a build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]

Upd. empirically found. disabling babel-minify-webpack-plugin resolves the error. Ie error during minification via Babel Webpack Minify plugin
April 4th 20 at 00:48
1 answer
April 4th 20 at 00:50
ie it turns out that you need to remove the babel minify. But if it is necessary for me, how to solve the problem?
Here he do not know the question is open. - Jules commented on April 4th 20 at 00:53

Find more questions by tags JavaScriptWebpack