Open edsadr opened 6 years ago
Thank you for providing this info! Do you know if this app has any lock files as well, like a package-lock.json?
@juliangruber just got the answer from the customer, they don't have locks files neither for npm or yarn, here is the package.json for the project when this is failing:
{
"name": "time-tracking",
"version": "1.0.0",
"description": "Time tracking app",
"main": "app.js",
"scripts": {
"serve": "serve ."
},
"repository": {
"type": "git"
},
"keywords": [
"time",
"track",
"angular",
"node",
"javascript",
"tutorial"
],
"license": "MIT",
"dependencies": {
"angular": "^1.5.3",
"angular-route": "^1.5.3",
"angular-ui-bootstrap": "^1.3.2",
"angular-ui-calendar": "^1.0.2",
"bootstrap": "^3.3.6",
"fullcalendar": "^3.0.0-beta",
"jasmine": "^2.4.1",
"jquery": "^2.2.2",
"karma": "^0.13.22",
"karma-ng-html2js-preprocessor": "^1.0.0",
"lodash": "^4.11.1",
"moment": "^2.14.1"
}
}
Trying to reproduce with the above package.json
and without a package-lock.json
worked for me:
Additionally, if you make api.nodesource.com
inaccessible from a machine, ncm-ci handles it:
I wonder if the restrictive VPN messes with the api response in any other way? Also, which OS is this, and @bnb did you try with their node version?
@juliangruber I tried with their node version, worked as expected. Judging by the screenshot @edsadr provided, it's a Linux distro (not sure which). I'm on macOS.
NCM-CI Fails to start
Trying to execute the tool in a Linux server connected to a restrictive VPN, it fails without providing info about the issue