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

Meteor 1.3 compatibility #37

Closed
UnconditionedLife opened this issue Apr 6, 2016 · 2 comments
Closed

Meteor 1.3 compatibility #37

UnconditionedLife opened this issue Apr 6, 2016 · 2 comments

Comments

@UnconditionedLife
Copy link

I continue to have problems with the 'Cannot find module fibers' error. I have tried both the -fiber and non-fiber versions of the driver and both cause Meteor not to load on my Mac OS X. I'm starting to think that this package is not compatible with Meteor 1.3, is that correct? If so, when do you think when you might have a 1.3 compatible version?

Thanks in advance!
Добрый день

@HannesHolste
Copy link
Contributor

HannesHolste commented Apr 28, 2016

Though @dr-dimitru hasn't updated this for 1.3, Meteor with this package still runs for me.

I had the fibers problem on OSX too, but I resolved it. See my post at: #26 (comment)

Neo4j is still treated as a global variable if you define it like this in, say, lib/neo4j.js:

Neo4j = new Neo4jDB(Meteor.settings.neo4j.url, {
    username: Meteor.settings.neo4j.username,
    password: Meteor.settings.neo4j.password
});

If you want to do it the ES6 way:

import { Meteor } from 'meteor/meteor';

export const Neo4j = new Neo4jDB(Meteor.settings.neo4j.url, {
    username: Meteor.settings.neo4j.username,
    password: Meteor.settings.neo4j.password
});

and then from a js file in project root:
import { Neo4j } from 'lib/neo4j.js';

@dr-dimitru
Copy link
Member

Hi everyone, thank you for contribution. I'm really sorry, but I can't put my hands on it right now. Let me make this clear - update and all testing from my side will be made until end of first half of 2016.

@HannesHolste thank you for reply in this thread.

dr-dimitru added a commit that referenced this issue Jan 24, 2017
 - No more CoffeeScript
 - Support for ES6 and import/export
 - Compatibility with `Neo4j@3.1.*`
 - Compatibility with `Meteor@1.4.*`
 - Better examples, no more CoffeeScript
 - Fix #37
 - Fix #36
 - Fix #33
 - Fix #31
@dr-dimitru dr-dimitru mentioned this issue Jan 24, 2017
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

No branches or pull requests

3 participants