Skip to content
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

Update Node to v6.11.2 #4

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update Node to v6.11.2 #4

wants to merge 2 commits into from

Conversation

sbeca
Copy link

@sbeca sbeca commented May 27, 2017

This PR updates Node to v6.11.2. It also updates all dependencies to the latest versions that are possible while maintaining support for Node v6.11.2.

I tried updating to Node v7.10.0 but it appears that SWIG doesn't yet support it as I got a bunch of compile errors so decided that v6.11.2 was a good compromise.

@sbeca
Copy link
Author

sbeca commented May 27, 2017

Tests are currently failing and I'm not exactly sure why. I'll have to look into it some more.

@zuker
Copy link
Owner

zuker commented Jun 1, 2017

@sbeca thanks for PR!
It seems that test should use weaker equality assertions (which don't check prototypes) with node v6
see:
https://travis-ci.org/zuker/box2d-native/builds/236650425#L7583
https://travis-ci.org/zuker/box2d-native/builds/236650425#L7559

demo/index.html Outdated
})();

let fps = 60;
setInterval(function() {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sbeca
Copy link
Author

sbeca commented Jun 3, 2017

Hi @zuker, I have updated the code so that all tests pass now and have switched back to using requestAnimationFrame. I have also rebased to remove the commit noise so this PR is ready for review again.

@sbeca
Copy link
Author

sbeca commented Aug 3, 2017

Hi @zuker, any update on this pull request?

@sbeca sbeca changed the title Update Node to v6.10.3 Update Node to v6.11.2 Aug 5, 2017
@endel
Copy link

endel commented Apr 13, 2018

Apparently, this pull request on SWIG fixes this: swig/swig#968

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.

3 participants