NPM run install scripts

Hi,
During the npm run dev step for 2.0.1 (current master HEAD) I run into this error:

---------------------------------------------------------------------------------------
root@akaunting:/var/www/akaunting.datatill.io/akaunting-master# npm run dev &
[1] 9879
root@akaunting:/var/www/akaunting.datatill.io/akaunting-master#
> akaunting@2.0.0 dev /var/www/akaunting.datatill.io/akaunting-master
> npm run development


> akaunting@2.0.0 development /var/www/akaunting.datatill.io/akaunting-master
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js


root@akaunting:/var/www/akaunting.datatill.io/akaunting-master#
95% emitting unnamed compat plugin
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! akaunting@2.0.0 development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the akaunting@2.0.0 development 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/2019-11-29T12_01_54_066Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! akaunting@2.0.0 dev: `npm run development`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the akaunting@2.0.0 dev 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/2019-11-29T12_01_54_098Z-debug.log

[1]+ Exit 1 npm run dev
root@akaunting:/var/www/akaunting.datatill.io/akaunting-master#
---------------------------------------------------------------------------------------

The error always presents itself at the `95% emitting unnamed compat plugin` point.

I will post the debug log next..

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev' ]
2 info using npm@6.11.3
3 info using node@v10.17.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle akaunting@2.0.0~predev: akaunting@2.0.0
6 info lifecycle akaunting@2.0.0~dev: akaunting@2.0.0
7 verbose lifecycle akaunting@2.0.0~dev: unsafe-perm in lifecycle true
8 verbose lifecycle akaunting@2.0.0~dev: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/akaunting.datatill.io/akaunting-master/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle akaunting@2.0.0~dev: CWD: /var/www/akaunting.datatill.io/akaunting-master
10 silly lifecycle akaunting@2.0.0~dev: Args: [ '-c', 'npm run development' ]
11 silly lifecycle akaunting@2.0.0~dev: Returned: code: 1 signal: null
12 info lifecycle akaunting@2.0.0~dev: Failed to exec dev script
13 verbose stack Error: akaunting@2.0.0 dev: `npm run development`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid akaunting@2.0.0
15 verbose cwd /var/www/akaunting.datatill.io/akaunting-master
16 verbose Linux 4.15.0-66-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
18 verbose node v10.17.0
19 verbose npm v6.11.3
20 error code ELIFECYCLE
21 error errno 1
22 error akaunting@2.0.0 dev: `npm run development`
22 error Exit status 1
23 error Failed at the akaunting@2.0.0 dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Pretty much stuck with the same issue. Any solution?

Pretty much stuck with the same issue. Any solution?

Have not gone further than this issue right now. Decided to stick to 1.3.7 for now until 2.0 is stable and easily installed.

Same issue in ubuntu 18 (VPS),,but working on may macOS local server.

I am having the same issue. Has anyone figured a way out?