bahmutov / bahmutov/next-update

Error: timed out waiting for NPM after 10000ms

Open
#141 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
557
Forks
16
PR merge metrics
No merged PRs in 30d

Description

Hi,

it raises an error on my env

```
$ next-update
next-update@3.6.0
- Tests if module's dependencies can be updated to the newer version without breaking the tests
installed in folder /usr/local/lib/node_modules/next-update
checking if the current state works
up to date in 33.203s
[!] 32 vulnerabilities found [7660 packages audited]
Severity: 4 low | 24 moderate | 4 high
Run `npm audit` for more detail

running test command
npm test
> meu-starter.ionic-v3@0.0.1 test /Users/victor/Dvpt/PROJECTS/meu-starter.ionic-v3
> karma start ./test-config/karma.conf.js --single-run --progress false --browsers Chrome

webpack: Compiled successfully.
webpack: Compiling...
...
> tests are passing at the start
checking NPM registry
ERROR testing next working updates
Error: timed out waiting for NPM after 10000ms
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5)
From previous event:
at nextVersions (/usr/local/lib/node_modules/next-update/src/registry.js:319:10)
at /usr/local/lib/node_modules/next-update/src/next-update.js:155:39
at RawTask.call (/usr/local/lib/node_modules/next-update/node_modules/asap/asap.js:40:19)
at flush (/usr/local/lib/node_modules/next-update/node_modules/asap/raw.js:50:29)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
```

I have the following installed

- osx@10.11.16
- next-update@3.6.0
- npm@6.0.0
- node@8.9.0

Please let me know if there is any more information I can give you, thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the failure with the reported next-update command and environment. Then inspect src/registry.js around line 319 and src/next-update.js around line 155, which the stack trace identifies as entry points; done means the NPM registry check no longer fails with this timeout.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.