From: oliver-cfc <oliver-cfc@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: llhttp: update to 2.0.5
Date: Tue, 12 May 2020 19:17:50 +0200 [thread overview]
Message-ID: <20200512171750.R3TDvD4tmTg5xHTdEw2BQ654KBJNfrUXVSb0aTt_7-k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21744@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
New comment by oliver-cfc on void-packages repository
https://github.com/void-linux/void-packages/pull/21744#issuecomment-627477613
Comment:
I'm pretty new to node so may be missing something but 'npm install ' fails with llhttp-2.0.5_1
```
$ npm i express
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <https://npm.community>
npm ERR! A complete log of this run can be found in:
npm ERR! /home/oliver/.npm/_logs/2020-05-12T17_11_37_457Z-debug.log
```
Downgrading to llhttp-1.1.4_1 allows it to work again
```
$ npm i express
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN nodeapi@1.0.0 No repository field.
+ express@4.17.1
added 50 packages from 37 contributors and audited 126 packages in 14.868s
found 0 vulnerabilities
```
Does this mean I need to wait for a node upgrade (current on nodejs-13.2.0_1) before upgrading llhttp again?
next prev parent reply other threads:[~2020-05-12 17:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 13:03 [PR PATCH] " rmccask
2020-05-11 18:28 ` [PR PATCH] [Merged]: " Hoshpak
2020-05-12 10:20 ` mustaqimM
2020-05-12 11:48 ` rmccask
2020-05-12 12:39 ` mustaqimM
2020-05-12 12:48 ` rmccask
2020-05-12 12:49 ` rmccask
2020-05-12 17:15 ` oliver-cfc
2020-05-12 17:17 ` oliver-cfc [this message]
2020-05-12 17:39 ` rmccask
2020-05-12 18:06 ` oliver-cfc
2020-05-12 19:12 ` rmccask
2020-05-13 1:01 ` rmccask
2020-05-13 7:15 ` mustaqimM
2020-05-13 12:29 ` rmccask
2020-05-13 12:38 ` mustaqimM
2020-05-14 15:55 ` oliver-cfc
2020-05-28 14:37 ` nathanblair
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200512171750.R3TDvD4tmTg5xHTdEw2BQ654KBJNfrUXVSb0aTt_7-k@z \
--to=oliver-cfc@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).