search

jspm / npm

NPM Location Service
19 stars 34 forks source link

Error on getOverride for jspm:npm #176

Closed priyabrat1801 closed 5 years ago

priyabrat1801 commented 5 years ago

Getting the below error while doing jspm install

 warn Error on getOverride for jspm:npm
      TypeError: "timeout" must be an unsigned integer
       at validateTimeout (child_process.js:623:11)
       at Object.exports.execFile (child_process.js:202:3)
       at exports.exec (child_process.js:139:18)

node: 9.4.0 npm: 5.6.0 jspm: 0.16.55

guybedford commented 5 years ago

Which version of jspm-npm are you using here? (from jspm/node_modules/jspm-npm)

Make sure the latest version is installed.

guybedford commented 5 years ago

Also jspm-registry should be at version 0.4.4.

priyabrat1801 commented 5 years ago

jspm-npm: 0.26.13 jspm-registry: 0.4.3

We are not installing these exclusively in package.json. Guess this is coming from the dependency on jspm package itself. Will it help to add these exclusively in the package.json?

guybedford commented 5 years ago

The problem is exactly not using 0.4.4 of jspm-registry. Npm should install the latest version by default, otherwise you should be able to just do the update manually.

On Tue, Jul 23, 2019 at 19:33 Priyabrat notifications@github.com wrote:

jspm-npm: 0.26.13 jspm-registry: 0.4.3

We are not installing these exclusively in package.json. Guess this is coming from the dependency on jspm package itself. Will it help to add these exclusively in the package.json?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/jspm/npm/issues/176?email_source=notifications&email_token=AAESFSSHFZZLDDMAZQNXNW3QA6IM3A5CNFSM4IGHFNGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UXCAQ#issuecomment-514420994, or mute the thread https://github.com/notifications/unsubscribe-auth/AAESFSSYGOZ7UW4USTJ7TN3QA6IM3ANCNFSM4IGHFNGA .

priyabrat1801 commented 5 years ago

Yes, we are using yarn and seems the versions were cached in the lock file and was not updating to the latest versions. We changed it to do the npm install and seems to be working.

Thanks @guybedford for the fix. we will check on the yarn issue separately.

priyabrat1801 commented 5 years ago

Closing for now.