Closed Vages closed 4 years ago
Sounds like a network issue. Axios (the HTTP lib) does not have a timeout set so it would hang indefinitely.
My suspicion too. Is there any hidden debug
flag for the CLI, @jeffijoe? (I'm downloading the repo in order to debug more, but simpler debugging would be great.)
I suppose you can use DEBUG=* typesync
, any libs that use debug
would start logging. :)
Turns out I can guarantee success by deleting (only) the line in devDependencies for webpack
. That's strange.
I'll try checking with some of my team mates to see if they can reproduce this.
I got 5 teammates to try and reproduce the bug, all using the same node version. One of my teammates uses Linux, while the rest uses MacOS. Only one was able to reproduce the bug, he was on Mac OS.
I was able to solve the issue for me by upgrading to the latest version of node 12. I'm therefore closing the issue, although this didn't help my team mate. We've not found any consistency regarding MacOS versions (10.15 vs. 10.14).
That's odd, I am on macOS as well, and I also use Webpack.
Yeah. Feel free to comment more if you're interested in drilling down into this, but until more users report similar problems, I don't think it's a good use of time.
Hi!
Thanks for a great package.
npx typesync
(v0.7.0 as well as v0.6.1) often hangs indefinitely. I tried letting the process run for one hour before posting this issue. No types are found. Other times everything works out fine – and that takes less than 60 seconds. I have not found any pattern.I have tried connecting to the Internet through
None of these seem to guarantee either success or failure. (As for success percentage, I've not made any thorough notes.)
My project has the following
package.json
. Note that@myscope/some-package
(a pseudonym for a package that I've had to redact) is configured to be fetched from an alternative registry, as seen here: https://docs.npmjs.com/files/npmrc#comments I have tried deleting@myscope/some-package
, to no avail.