-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Confusing Node.js version support #1066
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks! I will include instructions in the pg-pool library on how to node-postgres and therefore pg-pool both should support node back to On Tuesday, June 28, 2016, Vitaly Tomilov [email protected] wrote:
|
I've updated the pg-pool readme with better instructions on how to use it in versions of node which do not support Promises natively, and I've made the tests pass in older versions of node by removing the es6 stuff in the tests! Thanks. 😄 |
Great job! 😄 |
Uh oh!
There was an error while loading. Please reload this page.
The library itself is being tested against Node.js 0.10, till the latest, while everything has been moved to use the new
pg-pool
, which uses ES6 promises, and restricts you to Node.js 4.x and later.This creates confusion among users, and presumably a mess during deployment when the target server suddenly has a pre-4.x version of Node.js.
Check out another recent question I answered: error in pg-pool module when using postgres module with nodejs and heroku.
I believe that for this library it is very important to continue supporting Node.js 0.10 fully, which is still used by many, and will be for some time.
As for the promises, if somebody really wants to use them properly - you can tell them to use
pg-promise
, which will work under any Node.js version. I honestly don't think that promises should be used on this level, which is essentially a kernel for other libraries, and should remain to be that way 😉The text was updated successfully, but these errors were encountered: