error log terminal NPM

$ npm run build

> ffxiv-cmskin@2.2.0 build /Users/lili/Documents/GitHub/cmskin
> ESLINT=none roadhog build && gulp html

Build failed: Cannot read property 'compilation' of undefined
TypeError: Cannot read property 'compilation' of undefined
    at ProgressPlugin.apply (/Users/lili/Documents/GitHub/cmskin/node_modules/webpack/lib/ProgressPlugin.js:170:19)
    at Compiler.apply (/Users/lili/Documents/GitHub/cmskin/node_modules/tapable/lib/Tapable.js:375:16)
    at webpack (/Users/lili/Documents/GitHub/cmskin/node_modules/af-webpack/node_modules/webpack/lib/webpack.js:33:19)
    at buildWebpack (/Users/lili/Documents/GitHub/cmskin/node_modules/af-webpack/lib/build.js:100:41)
    at build (/Users/lili/Documents/GitHub/cmskin/node_modules/af-webpack/lib/build.js:117:3)
    at /Users/lili/Documents/GitHub/cmskin/node_modules/roadhog/lib/build.js:77:24
    at new Promise (<anonymous>)
    at Object._default [as default] (/Users/lili/Documents/GitHub/cmskin/node_modules/roadhog/lib/build.js:46:10)
    at Object.<anonymous> (/Users/lili/Documents/GitHub/cmskin/node_modules/roadhog/lib/scripts/build.js:22:28)
    at Module._compile (internal/modules/cjs/loader.js:936:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:947:10)
    at Module.load (internal/modules/cjs/loader.js:790:32)
    at Function.Module._load (internal/modules/cjs/loader.js:703:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:999:10)
    at internal/main/run_main_module.js:17:11
[00:17:19] Requiring external module @babel/register
/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/config/full.js:135
    throw e;
    ^

Error: [BABEL] /Users/lili/Documents/GitHub/cmskin/gulpfile.babel.js:
As of v7.0.0-beta.55, we've removed Babel's Stage presets.
Please consider reading our blog post on this decision at
https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets
for more details. TL;DR is that it's more beneficial in the
  long run to explicitly add which proposals to use.

For a more automatic migration, we have updated babel-upgrade,
https://github.com/babel/babel-upgrade to do this for you with
"npx babel-upgrade".

If you want the same configuration as before:

{
  "plugins": [
    // Stage 0
    "@babel/plugin-proposal-function-bind",

    // Stage 1
    "@babel/plugin-proposal-export-default-from",
    "@babel/plugin-proposal-logical-assignment-operators",
    ["@babel/plugin-proposal-optional-chaining", { "loose": false }],
    ["@babel/plugin-proposal-pipeline-operator", { "proposal": "minimal" }],
    ["@babel/plugin-proposal-nullish-coalescing-operator", { "loose": false }],
    "@babel/plugin-proposal-do-expressions",

    // Stage 2
    ["@babel/plugin-proposal-decorators", { "legacy": true }],
    "@babel/plugin-proposal-function-sent",
    "@babel/plugin-proposal-export-namespace-from",
    "@babel/plugin-proposal-numeric-separator",
    "@babel/plugin-proposal-throw-expressions",

    // Stage 3
    "@babel/plugin-syntax-dynamic-import",
    "@babel/plugin-syntax-import-meta",
    ["@babel/plugin-proposal-class-properties", { "loose": false }],
    "@babel/plugin-proposal-json-strings"
  ]
}

If you're using the same configuration across many separate projects,
keep in mind that you can also create your own custom presets with
whichever plugins and presets you're looking to use.

module.exports = function() {
  return {
    plugins: [
      require("@babel/plugin-syntax-dynamic-import"),
      [require("@babel/plugin-proposal-decorators"), { "legacy": true }],
      [require("@babel/plugin-proposal-class-properties"), { "loose": false }],
    ],
    presets: [
      // ...
    ],
  };
};
   (While processing: "/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/preset-stage-0/lib/index.js")
    at _default (/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/preset-stage-0/lib/index.js:9:9)
    at /Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/config/full.js:165:14
    at cachedFunction (/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/config/caching.js:33:19)
    at loadPresetDescriptor (/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/config/full.js:255:36)
    at /Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/config/full.js:77:21
    at Array.reduce (<anonymous>)
    at recurseDescriptors (/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/config/full.js:74:38)
    at loadFullConfig (/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/config/full.js:108:6)
    at loadOptions (/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/config/index.js:27:36)
    at OptionManager.init (/Users/lili/Documents/GitHub/cmskin/node_modules/@babel/core/lib/index.js:231:36)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ffxiv-cmskin@2.2.0 build: `ESLINT=none roadhog build && gulp html`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ffxiv-cmskin@2.2.0 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!    /.npm/_logs/2019-09-11T22_17_20_269Z-debug.log