Does autopublish have a purpose in Meteor 1.3+?

packages
1

The purpose of the autopublish package is to simplify app prototyping. However, when using Meteor 1.3+ with import/export, that benefit goes away, or am I wrong on that?

An example:

With this…

Foo = new Mongo.Collection('foo')

…I am able to do this in the (client) console…

However, with this…

import {Mongo} from 'meteor/mongo'
export const Foo = new Mongo.Collection('foo')

I get this…

So, I guess my question is - what purpose, if any, does autopublish have in a Meteor 1.3+ paradigm when using import/export?

2

Well you don’t have to write publications, that’s the main goal.

2 Likes