node v8.8 - HTTP2 issue?
See original GitHub issueHaving some issues with upgrade to node 8.8
Bankai falls over when a website reloads … I don’t get much more in the logs other than an ELIFECYCLE error.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! descartes@1.0.0 dev: `bankai start index.js`
npm ERR! Exit status 1
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (15 by maintainers)
Top Results From Across the Web
HTTP/2 | Node.js v19.3.0 Documentation
The http2 Core API is much more symmetric between client and server than the http API. For instance, most events, like 'error' ,...
Read more >node.js - NodeJS native http2 support
--expose-http2 flag enables experimental HTTP2 support. This flag can be used in nightly build (Node v8.4.0) since Aug 5, 2017 (pull request).
Read more >HTTP/2 in Node.JS Core - Level Up Coding
In our latest blogposts, we mentioned that a version of HTTP/2 was starting to be implemented under the nodejs/http2 repository, but it was...
Read more >What's new in Node.js 9?
Node.js 8 became the LTS version on 31 October 2017, and Node.js 9 became the ... You can start using HTTP/2 with the...
Read more >Difference between HTTP/2 and HTTP/1.1
These are the drawbacks that lead to the creation of HTTP/2: The first problem is HTTP/1.1 transfer all the requests & responses in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Opened up an issue on Node core to figure this out how to fix this https://github.com/nodejs/node/issues/16666
Dang, yeah tried it too today, and things aren’t working the way it’s supposed to be. On my end we’re experiencing a double close error, which might be an artifact from the pre
v8.8.x
days. Going to dig into this a bit soon.