v7.17.1 - stream issue in Node.js < v8
See original GitHub issueIn v7.17.1, with pg-query-stream
3.0.0, I am getting error under Node.js < v8
TypeError: stream.destroy is not a function
For example, I am testing it under Node.js v7.10.1
@brianc It seems that after changing from method close
to method destroy
on the stream, we lost compatibility with Node.js v7 and earlier.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
node/CHANGELOG_V17.md at main · nodejs/node - GitHub
This release fixes an issue introduced in Node.js v17.7.0 with some URLs that contain @ . This issue affected yarn 1. This version...
Read more >Errors | Node.js v18 API
AssertionError s are a special class of error that can be triggered when Node.js detects an exceptional logic violation that should never occur....
Read more >HTTP | Node.js v19.3.0 Documentation
Produces a socket/stream to be used for HTTP requests. ... Added in: v8.1.0 ... host <string> A domain name or IP address of...
Read more >Download & Update Node.js to the Latest Version! Node v19 ...
Node.js 19 is here! Highlights include the update of the V8 JavaScript engine to 10.7, HTTP(s)/1.1 KeepAlive enabled by default, and ESM ...
Read more >Node.js - CloudBees Documentation
CodeShip uses nvm to manage different Node.js versions. ... v6.17.1 v7.0.0 v7.1.0 v7.2.0 v7.2.1 v7.3.0 v7.4.0 v7.5.0 v7.6.0 v7.7.0 v7.7.1 v7.7.2 v7.7.3 ...
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
Mostly that node 8 is end of life…I think following along w/ the node LTS release cycle is a pretty manageable way to figure out which versions of node to target for support from pg. I’d like modernize the codebase of pg & use newer features of v8 that don’t exist in older versions of node (async/await for example!). I think for folks running 2-3 year old verions of node they’ll need to stay pinned to older versions of pg.
Ah thanks for the heads up, I’ll include a note about that in the changelog. 💃 Since it’s semver major I’m fine w/ it dropping support for node < 8. I’m planning on dropping support for node < 10 in a few days w/ pg@8.0 too! 👏