default-input: Catch errors from npa

[legodude17]

Before:

After:

Catches errors from npa instead of letting them propagate

[addaleax]

ping @zkat @iarna ? This was just brought up on a Node.js tracker :)

[legodude17]

Thanks for the approval @addaleax! Did the change you suggested.

[mmmm1998]

Well, not good, that I burst in this pull request, but It's usfull change, any status changing (merge/close)?

[legodude17]

I'm just waiting for a review from a maintainer.

[zkat]

👍 thanks! This is a good thing to catch!

[legodude17]

Thank you!

[smashraid]

Hi I would like to know if this problem is related to this. I executed npm init as Administrator

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'init' ]
2 info using npm@5.6.0
3 info using node@v9.10.1
4 silly package data { name: 'angulp',
4 silly package data version: '1.0.0',
4 silly package data description: 'Gulp test',
4 silly package data main: 'main.js',
4 silly package data scripts: { test: 'echo "Error: no test specified" && exit 1' },
4 silly package data author: 'Saulo Tsuchida',
4 silly package data license: 'ISC' }
5 info init written successfully
6 verbose stack Error: ENOENT: no such file or directory, open 'C:\Users\saulo_000\Documents\Development\angularjs\package.json'
7 verbose cwd C:\Users\saulo_000\Documents\Development\angularjs
8 verbose Windows_NT 10.0.16299
9 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "init"
10 verbose node v9.10.1
11 verbose npm v5.6.0
12 error path C:\Users\saulo_000\Documents\Development\angularjs\package.json
13 error code ENOENT
14 error errno -4058
15 error syscall open
16 error enoent ENOENT: no such file or directory, open 'C:\Users\saulo_000\Documents\Development\angularjs\package.json'
17 error enoent This is related to npm not being able to find a file.
18 verbose exit [ -4058, true ]

[smashraid]

Hi all I was able to fix my problem and is related to an option in windows 10 Controlled folder access was ON
I hope this help someone

[legodude17]

@smashraid try updating npm