Safe_browser build error. Failed at the @ pack-authenticator script. code ELIFECYCLE

Support
1

I’m trying to build the safe_browser 0.2.0.
I however got stuck at step 4.

[admin@UBS-Dev safe_browser-0.2.0]$ npm run pack-authenticator
...

npm
 ERR! code ELIFECYCLE

npm
 ERR! 
errno 1

npm 
ERR!
 @ pack-authenticator:unix: `sh ./scripts/pack_authenticator.sh ""`
npm 
ERR!
 Exit status 1
npm
 ERR!
 
npm
 ERR!
 Failed at the @ pack-authenticator:unix 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!
     /home/admin/.npm/_logs/2017-05-30T04_56_27_388Z-debug.log

Pack Authenticator exited with code 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ pack-authenticator: `node ./scripts/main.js --authenticator`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ pack-authenticator 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!     /home/admin/.npm/_logs/2017-05-30T04_56_27_418Z-debug.log

[admin@UBS-Dev safe_browser-0.2.0]$ cat /home/admin/.npm/_logs/2017-05-30T04_56_27_418Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'pack-authenticator' ]
2 info using npm@4.6.1
3 info using node@v7.10.0
4 verbose run-script [ 'prepack-authenticator',
4 verbose run-script   'pack-authenticator',
4 verbose run-script   'postpack-authenticator' ]
5 info lifecycle @~prepack-authenticator: @
6 silly lifecycle @~prepack-authenticator: no script for prepack-authenticator, continuing
7 info lifecycle @~pack-authenticator: @
8 verbose lifecycle @~pack-authenticator: unsafe-perm in lifecycle true
9 verbose lifecycle @~pack-authenticator: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/admin/Downloads/safe_browser-0.2.0/node_modules/.bin:/usr/local/bin:/usr/bin:/bin
10 verbose lifecycle @~pack-authenticator: CWD: /home/admin/Downloads/safe_browser-0.2.0
11 silly lifecycle @~pack-authenticator: Args: [ '-c', 'node ./scripts/main.js --authenticator' ]
12 silly lifecycle @~pack-authenticator: Returned: code: 1  signal: null
13 info lifecycle @~pack-authenticator: Failed to exec pack-authenticator script
14 verbose stack Error: @ pack-authenticator: `node ./scripts/main.js --authenticator`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:194:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:194:7)
14 verbose stack     at maybeClose (internal/child_process.js:899:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid @
16 verbose cwd /home/admin/Downloads/safe_browser-0.2.0
17 verbose Linux 4.10.16-gnu-1
18 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "pack-authenticator"
19 verbose node v7.10.0
20 verbose npm  v4.6.1
21 error code ELIFECYCLE
22 error errno 1
23 error @ pack-authenticator: `node ./scripts/main.js --authenticator`
23 error Exit status 1
24 error Failed at the @ pack-authenticator script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
2 Likes
2

Hi @folaht, this must be due to a couple of pending PRs currently under review on safe_client_libs and safe_app plugin which should be merged shortly, I can reply here when that’s done so you can try it again if you like.

5 Likes
3

Also, there are threads about building these on the developer forum - but @bochaco seems to have answered your question.

1 Like
4

Good, I’ll wait then.

5

How soon is soon is shortly?

6

Hi @folaht, you can give it a try again now, it should build just fine.

3 Likes
7

hello sir, i still get this type of error can you please help ?

npm WARN invalid config loglevel=“notice”

angular-quickstart@1.0.0 build C:\projects\myapp
tsc -p src/

src/app/components/user.component.ts(25,5): error TS2322: Type ‘{ street: “Arohi club road”; city: “Ahmedabad”; state: “gujrat”; }’ is not assignable to type ‘address’.
Types of property ‘street’ are incompatible.
Type ‘“Arohi club road”’ is not assignable to type ‘“string”’.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! angular-quickstart@1.0.0 build: tsc -p src/
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the angular-quickstart@1.0.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! C:\Users\Kajal Shah\AppData\Roaming\npm-cache_logs\2017-06-11T06_49_11_917Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! angular-quickstart@1.0.0 prestart: npm run build
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the angular-quickstart@1.0.0 prestart 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! C:\Users\Kajal Shah\AppData\Roaming\npm-cache_logs\2017-06-11T06_49_11_996Z-debug.log

8

What does the 2017-06-11T06_49_11_996Z-debug.log file say and what’s in user.component.ts?

9

This topic was automatically closed after 60 days. New replies are no longer allowed.