Meteor 1.3: Uncaught Error: use "new" to construct a Mongo.Collection
See original GitHub issueWhen I create a collection
Parties = new Ground.Collection('parties', { connection: null });
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
[question]usage with meteor 1.3 · Issue #153 · GroundMeteor/db ...
Do you know any issues to use the alpha version of GroundDB with 1.3? ... Meteor 1.3: Uncaught Error: use "new" to construct...
Read more >Error: collection declared twice - Meteor forums
Hi, I have an error message saying Uncaught Error: There is already a collection named 'trackings' But it is declared just once in...
Read more >Meteor-React tutorial, can't see Mongo data in the web-browser
So either Meteor can't fetch data from Mngo or there's something wrong with the rendering component. Sorry, if this is too newbie question...
Read more >Astronomy Documentation
import { Class } from 'meteor/jagi:astronomy'; const Posts = new Mongo.Collection('posts'); const Post = Class.create({ name: 'Post', collection: Posts, ...
Read more >Urigo/angular-meteor - Gitter
https://angular-meteor.com/tutorials/whatsapp2/ionic/setup ... Uncaught ReferenceError: Mongo is not defined at new Collection (modules.js?hash=cfb4d1f…
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@raix Thanks for the awesome work. The issue is resolved
2.0.0-alpha.2
https://github.com/GroundMeteor/db/issues/153#issuecomment-206125703