Is not working inside of Docker Container

[kilpatty]

I built a docker container that is only built to run gulp as a task runner. I have tried implementing npm-check-updates into this process so that I could make it easier to update the packages. When I run ncu -u I get a failure error:
Invalid package file from stdin. Error details:
No data, empty input at 1:1

^
(my docker container) exited with code 1.

I know that the package file exists and works correct, as if I only run npm install and gulp everything runs as expected.

If you want to recreate this issue the code for the container I am using is located here:
https://github.com/Skilgarriff/docker-develop
Simply download this then uncomment Line 11 and comment Line 15, 5 and 8 in the dockerfile.
run Docker-compose build, then docker-compose up and the error should be replicated.

[raineorshine]

Try using the --packageFile option. Some nonstandard usages of ncu trigger its stdin mode.

[kilpatty]

Used the --packageData option instead and it worked! Can close, thanks for the help

[raineorshine]

Great
On Sun, Feb 28, 2016 at 3:03 PM Sean Kilgarriff notifications@github.com
wrote:

Used the --packageData option instead and it worked! Can close, thanks for
the help

—
Reply to this email directly or view it on GitHub
#215 (comment)
.

[rzr]

IMHO, ncu could detect that stdin is not available and then fallback to desired behaviour described above.
has this been reported anywhere ?

For the record here is the reported error:

ncu -a
Invalid package file from stdin. Error details:
Bad numeric literal - "." at 1:1
package.json

ncu --version
2.15.0

ncu -a  --packageFile package.json 

[raineorshine]

@rzr Yes, there is an issue that several people have reported with stdin false positives, although nobody has investigated more thoroughly yet. I am unable to reproduce on my end.

See #136