Skip to content

Update all dependencies to their latest versions. #621

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

Merged
merged 1 commit into from
Aug 6, 2014

Conversation

joskuijpers
Copy link
Contributor

Almost all dependencies were outdated.
I used npm outdated to find the latest versions. Unit tests still run.

The update of generic-pool is quite important, as it contains this fix: coopernurse/node-pool#64

@brianc
Copy link
Owner

brianc commented Aug 6, 2014

awesome! thanks for this! 👏

brianc added a commit that referenced this pull request Aug 6, 2014
Update all dependencies to their latest versions.
@brianc brianc merged commit 3d4ae51 into brianc:master Aug 6, 2014
@joskuijpers joskuijpers deleted the update_deps branch August 7, 2014 09:58
@ricardograca
Copy link

OTOH the new Nan is causing builds to fail on Node 0.11.x and generating deprecation warnings on older versions.

@joskuijpers
Copy link
Contributor Author

Yeah, been following that. Unfortunately I did not test 0.11 on my own machine. Do remember though that 0.11 is still 'unstable'.

V8 has been having some major API changes in last 10 minor versions, and Node 0.10 is VERY far behind on Chrome, because it depended a lot on the old api.

I would suggest using the previous version of node-postgres when building with 0.11.

@brianc
Copy link
Owner

brianc commented Aug 19, 2014

Been playing with NaN locally and hopefully I can update it soon!

On Tuesday, August 19, 2014, Jos Kuijpers notifications@github.com wrote:

Yeah, been following that. Unfortunately I did not test 0.11 on my own
machine. Do remember though that 0.11 is still 'unstable'.

V8 has been having some major API changes in last 10 minor versions, and
Node 0.10 is VERY far behind on Chrome, because it depended a lot on the
old api.

I would suggest using the previous version of node-postgres when building
with 0.11.


Reply to this email directly or view it on GitHub
#621 (comment).

@santigimeno
Copy link
Contributor

@brianc see #630

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants