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

⬆️ nan@1.5.1 for iojs support #110

Merged
merged 1 commit into from
Jan 20, 2015
Merged

⬆️ nan@1.5.1 for iojs support #110

merged 1 commit into from
Jan 20, 2015

Conversation

jonathanong
Copy link
Contributor

No description provided.

@chahn
Copy link

chahn commented Jan 16, 2015

👍

1 similar comment
@coma
Copy link

coma commented Jan 16, 2015

👍

@timoxley
Copy link

nodejs/node#456

@christkv
Copy link
Contributor

please provide instructions on how to set up a working iojs env so I can test this.currently there seems to be no straight forward way to do this on osx that I can find. I need to test first before accepting the pull request.

@chahn
Copy link

chahn commented Jan 16, 2015

io.js should soon emerge in homebrew. There's already a PR: Homebrew/legacy-homebrew#35853

@christkv
Copy link
Contributor

does not solve my node-gyp issues. I need to get to where I can do a node-gyp rebuild

@jonathanong
Copy link
Contributor Author

@christkv if you install iojs, running npm install or npm rebuild will work. just don't update npm or anything as npm/node-gyp doesn't fully support iojs yet. you have to use what's included with iojs.

@jonathanong jonathanong changed the title ⬆️ nan@1.5.0 for iojs support ⬆️ nan@1.5.1 for iojs support Jan 16, 2015
@salzhrani
Copy link

+1

@christkv christkv merged commit 106e3ab into mongodb:master Jan 20, 2015
@jonathanong jonathanong deleted the patch-1 branch January 20, 2015 07:01
@chahn
Copy link

chahn commented Jan 20, 2015

Yah. Thanks.

@secretfader
Copy link

When can we expect a release of this fix? The sooner it's out, the better for modules that depend on js-bson and their compatibility with io.js.

@salzhrani
Copy link

Would love a release, please.

@hectorfhurtado
Copy link

+1

@christkv
Copy link
Contributor

it's been out awhile already

@hectorfhurtado
Copy link

ouch. Since installed io.js I've see this error on my current project

{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }
js-bson: Failed to load c++ bson extension, using pure JS version

@ZloyDyadka
Copy link

@jdhiro
Copy link

jdhiro commented Mar 15, 2015

It looks like there are two issues pointing at each other that are both closed? I'm still getting this with the latest version of everything installed and rebuilt.

@tiefenb
Copy link

tiefenb commented Mar 26, 2015

I also still getting this with the latest version and iojs 1.6.x

@tiefenb
Copy link

tiefenb commented Mar 26, 2015

I am getting:

[Error: Module did not self-register.]
js-bson: Failed to load c++ bson extension, using pure JS version

@christkv
Copy link
Contributor

if you upgrade your io.js or node version you need to completely flush every npm module as the V8 C++ api's changed making every single native module binary incompatible. It's even worse with io.js as every possible minor upgrade might break.

@tiefenb
Copy link

tiefenb commented Mar 26, 2015

thanks, it works now

@hectorfhurtado
Copy link

HI, I reinstalled every module but I'm still getting this error

{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }
js-bson: Failed to load c++ bson extension, using pure JS version

I'm on a Windows 7 32bit machine. Running iojs 1.6.2 and mongodb version 2.6.7

@christkv
Copy link
Contributor

you need the whole tool chain to build this. Anyway that is a warning not a failure. It falls back to the pure js implementation of the parser. Just ignore it.

@toni89
Copy link

toni89 commented May 29, 2015

still getting that message with iojs@2.1.0 and bson@0.3.2.

js-bson: Failed to load c++ bson extension, using pure JS version
[Error: Module did not self-register.]

What can i do?

@hectorfhurtado
Copy link

Hi, I encountered that I was using an outdated version of mongodb: Ididn't get noticed until I used npm oudated, once I changed my package.json and updated, everything runs normal now. Maybe that helps you @toni89

@toni89
Copy link

toni89 commented May 30, 2015

@hectorfhurtado thank you, but i have already the newest 2.0.33 version installed. maybe this is an mac os issue!??

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.