What I Wanted to Do
npm install under firstname.lastname@example.org and email@example.com (included by default)
What Happened Instead
The process log a
npm ERR! asyncWrite is not a function all the time
I think my code is not significant here, but I see the error doing a npm install after clone https://github.com/microlinkhq/www.
A complete npm debug stack trace here:
If I switch to
firstname.lastname@example.org that has
email@example.com, it works like a charm.
Then the thing that was trying to do was update npm to the last version.
I can’t update npm from
firstname.lastname@example.org because the process throws another error related with stream:
npm ERR! pna.nextTick is not a function
so instead I downgrade to
email@example.com and install the last npm version available
The last npm version available is
firstname.lastname@example.org, that is curious because is the same that the npm version included in the
But this time it works fine. Looks like
email@example.com include a breaking change related with stream under the hood and the npm process doesn’t like it.
❯ node --version v10.3.0 ❯ npm --version 6.1.0