backpack npm run dev faild

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'dev' ]
2 info using npm@5.3.0
3 info using node@v8.4.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle news@1.0.0~predev: news@1.0.0
6 info lifecycle news@1.0.0~dev: news@1.0.0
7 verbose lifecycle news@1.0.0~dev: unsafe-perm in lifecycle true
8 verbose lifecycle news@1.0.0~dev: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/andreyleonov/Desktop/news-ex/node_modules/.bin:/usr/local/opt/curl/bin:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle news@1.0.0~dev: CWD: /Users/andreyleonov/Desktop/news-ex
10 silly lifecycle news@1.0.0~dev: Args: [ '-c', 'backpack dev' ]
11 silly lifecycle news@1.0.0~dev: Returned: code: 1 signal: null
12 info lifecycle news@1.0.0~dev: Failed to exec dev script
13 verbose stack Error: news@1.0.0 dev: `backpack dev`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:289:16)
13 verbose stack at emitTwo (events.js:125:13)
13 verbose stack at EventEmitter.emit (events.js:213:7)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
13 verbose stack at emitTwo (events.js:125:13)
13 verbose stack at ChildProcess.emit (events.js:213:7)
13 verbose stack at maybeClose (internal/child_process.js:927:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
14 verbose pkgid news@1.0.0
15 verbose cwd /Users/andreyleonov/Desktop/news-ex
16 verbose Darwin 16.7.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev"
18 verbose node v8.4.0
19 verbose npm v5.3.0
20 error code ELIFECYCLE
21 error errno 1
22 error news@1.0.0 dev: `backpack dev`
22 error Exit status 1
23 error Failed at the news@1.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 ]

Start by reproducing `npm run dev` with Node.js v8.4.0 and npm 5.3.0, then inspect the additional output from the `backpack dev` command. The issue is resolved when the dev script completes successfully and starts the development build.

Written by the indexing model from the issue text.