0.9.1 release candidate! Meteor developer accounts organizations, backwards compatible API changes

[Avital Oliver]

Hi everyone,

The upcoming 0.9.1 release is almost ready! It includes a few things:

* Meteor developer accounts organizations. One of the top requests after 0.9.0! You can now add teams of people as authorized users for packages or apps.

* Some changes to the Blaze and UI APIs. The changes are mostly in APIs that were previously undocumented (and are now documented!). Those changes have been kept backwards compatible when possible.

* Renaming some packages and globals in preparation for 1.0 (such as Deps -> Tracker). These should all be backwards compatible.

---

We're releasing a preview now, so that you can try your apps and packages. You can upgrade your app by running `meteor update --release 0.9.1-rc2`.

If you're using iron:router, you'll have to do a bit more: (This will not be necessary once 0.9.1 is released)

    meteor remove iron:router

    meteor update --release 0.9.1-rc2

    meteor add iron-...@0.9.2-rc0

Let us know if you run into any issues or have any questions about how to port your code!

[Arunoda Susiripala]

This means, iron-router is going to be a core package? or you meant iron:rou...@0.9.2-rc0.

---

Arunoda Susiripala

I curate Meteor Weekly - Check it out!

--
You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.
For more options, visit https://groups.google.com/d/optout.

[Emily Stark]

Oops -- Avital meant `meteor add iron:rou...@0.9.2-rc0` in the last step. Thanks for catching that, Arunoda!

Also a big thanks to Chris Mather for working with us to make sure that there's a version of iron:router available for use with 0.9.1-rc2. :)

[Arunoda Susiripala]

nice.

---

Arunoda Susiripala

I curate Meteor Weekly - Check it out!

[Morten Henriksen]

Hi, just a quick question,

so users and organisations live in the same prefix namespace? before the time of mps I created a user "cfs" now can I remove this and add an org "cfs" instead?

Kind regards Morten

[Emily Stark]

Hi Morten -- that's correct, users and organizations are in the same namespace. We'll be working out something soon (probably next week) for users that should be converted into organizations.

[Morten Henriksen]

Hi Emily,

Sounds really nice, getting a lot of hits/issues on the collectionfs project on this - its a bleeding edge Meteor community hungry for new tech here :)

Btw. Will it be possible to remove failed /wrong packages on the package server? (kind of the reason for a lot off issues, at the moment its a bit messed up where cfs packages are prefixed with different users from the team, a bit puzzled / inconsistent)

And is there a way to see what packages raix has published? (apologize if already a feature)

Venlig hilsen

Morten N. O. Nørgaard Henriksen

Grøn idé ApS - 30 13 12 41

You received this message because you are subscribed to a topic in the Google Groups "meteor-core" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meteor-core/s-xGYQ3gBkc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meteor-core...@googlegroups.com.

[Emily Stark]

Btw. Will it be possible to remove failed /wrong packages on the package server? (kind of the reason for a lot off issues, at the moment its a bit messed up where cfs packages are prefixed with different users from the team, a bit puzzled / inconsistent)

It will be possible to mark packages as deprecated, and maybe eventually to delete them, but I'm not sure on the exact timeline there.

 

And is there a way to see what packages raix has published? (apologize if already a feature)

I think `meteor search "raix:"` will more or less do what you want for that.

[Max Harris]

Can anyone point me to an example app that uses the new Blaze APIs?

I'm trying to follow the documentation, but what I have so far keeps getting stuck in a re-rendering cycle. I must be doing something wrong, but I have no idea what the issue is.

- Max

[Zoltan Olah]

I'm trying to publish a package targetted at the new RC and am having some trouble. I'm seeing:

```

meteor publish --create

Refreshing package metadata. This may take a moment.

Reading package...

Figuring out the best package versions to use. This may take a moment.

Could not resolve the specified constraints for this package:

Error: conflict: ej...@1.0.0 vs 1.0.1-rc0

```

My package.js looks like:

```

  api.versionsFrom('MET...@0.9.1-rc2');

  

  api.use(['deps', 

    'iron:rou...@0.9.2-rc0', 

    'percolate:mome...@0.0.1'], 

  'client');

```

Is this a bug? Am I doing something wrong. Is it possible to get more verbose debugging info from the constraint solver on where it's detected a problem?

​-Zol

[Emily Stark]

Hey Zol,

What does percolate:mom...@0.0.1's package.js file look like? If that version of percolate:momentum uses, say, `api.versionsFrom('0.9.0')`, then that will cause a conflict (for now) because we don't treat ej...@1.0.1-rc0 as compatible with a constraint on ej...@1.0.0. I believe this is an issue with dashed version numbers that we're going to fix soon, but for now you should be able to get things to work by publishing a version of percolate:momentum that uses `api.versionsFrom('0.9.1-rc2')` and depending on that.

Hope that helps,

Emily

--

[Emily Stark]

Hey David,

I think that 0.9.0-rc12 might have had some bugs that prevented updates from working properly. Can you try installing the latest release, 0.9.0.1, fresh by doing `rm -rf ~/.meteor` and `curl https://install.meteor.com/ | sh`?

Thanks,

Emily

On Fri, Aug 29, 2014 at 3:18 PM, David Collier <d...@biz.pikkle.com> wrote:

I'm getting an error:

> meteor update --release 0.9.1-rc2

0.9.1-rc2: unknown release.

however there does seem to be a tag with that name, so assume there is something in the meteor release system preventing this:

https://github.com/meteor/meteor/tree/release/METEOR%400.9.1-rc2

btw I am trying this in an app dir which is already 0.9.0

ptest> meteor update --release 0.9.1-rc2                               

0.9.1-rc2: unknown release.

ptest> meteor --version

Meteor 0.9.0-rc12

ptest> meteor update

This project is already at Meteor 0.9.0-rc12, the latest release.

ptest> 

--
You received this message because you are subscribed to the Google Groups "meteor-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-talk...@googlegroups.com.

[Zoltan Olah]

Thanks Emily, I suspected exactly what you're suggesting and published a new version of momentum that depends on `api.versionsFrom('0.9.1-rc2')` but to my surprise I'm seeing the same error. Could something be cached?

momentum/package.js:

```

Package.describe({

  summary: "Reactive animations",

  version: "0.0.2",

  name: "percolate:momentum",

  git: "https://github.com/percolatestudio/meteor-momentum.git"

});

Package.on_use(function (api) {

  api.versionsFrom('MET...@0.9.1-rc2');

  api.use(['templating', 'check', 'jquery', 'underscore'], 'client');

  

  api.add_files([

    ...

  ], 'client');

  api.export(['Momentum'], 'client');

});

```

momentum-iron-router/package.js:

```

Package.describe({

  summary: "A momentum plugin for transitioning Iron Router pages",

  version: "0.0.1",

  name: "percolate:momentum-iron-router",

  git: "https://github.com/percolatestudio/momentum-iron-router.git"

});

Package.on_use(function (api, where) {

  api.versionsFrom('MET...@0.9.1-rc2');

  

  api.use(['deps', 

    'iron:rou...@0.9.2-rc0', 

    'percolate:mome...@0.0.2'], 

  'client');

  

  api.add_files('momentum-transitioner.js', ['client']);

});

```

Zoltan Olah

Partner/Engineer

http://percolatestudio.com

+1 415 696 4455

[Andrew Mao]

This is probably due to https://github.com/meteor/meteor/issues/2443?

On Friday, August 29, 2014 5:56:54 PM UTC-4, Zoltan Olah wrote:

I'm trying to publish a package targetted at the new RC and am having some trouble. I'm seeing:

```

meteor publish --create

Refreshing package metadata. This may take a moment.

Reading package...

Figuring out the best package versions to use. This may take a moment.

Could not resolve the specified constraints for this package:

Error: conflict: ej...@1.0.0 vs 1.0.1-rc0

```

My package.js looks like:

```

  api.versionsFrom('METEOR@0.9.1-rc2');

  

  api.use(['deps', 

    'iron:rou...@0.9.2-rc0', 

    'percolate:mome...@0.0.1'], 

  'client');

[Avital Oliver]

Andrew, yup.

--

You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.
For more options, visit https://groups.google.com/d/optout.

--

PS. I genuinely *really* like receiving feedback of any kind. Leave it anonymously at http://www.admonymous.com/avital

[Zoltan Olah]

Is there a plan to include more verbose output to help track down where in the dependency graph the conflict is detected? It would be very helpful.

Zoltan Olah

Partner/Engineer

http://percolatestudio.com

+1 415 696 4455

[Avital Oliver]

Hey Zol,

Maybe you need to also call `api.versionsFrom` in an `on_test` clause? We hit that earlier today. I don't think it's an issue with caching package versions incorrectly.

[Avital Oliver]

We've got another release candidate out. To update, run `meteor update --release 0.9.1-rc3`. If you're using iron-router:

    meteor remove iron:router

    meteor update --release 0.9.1-rc3

    meteor add iron-router@0.9.2-rc2

Changes from 0.9.1-rc0:

* Backwards compatibility with old packages that export templates
* Don't break apps on Chrome with cookies & local storage blocked
* A few more backwards compatible renames (Meteor.Collection -> Mongo.Collection, livedata package -> ddp package)

Give a whirl and let us know how it goes!

[Jan-Hendrik Mangold]

On Sep 2, 2014, at 19:01, Avital Oliver <avi...@meteor.com> wrote:

We've got another release candidate out. To update, run `meteor update --release 0.9.1-rc3`. If you're using iron-router:

    meteor remove iron:router

    meteor update --release 0.9.1-rc3

    meteor add iron-router@0.9.2-rc2

typo? shouldn’t that be

meteor add iron:rou...@0.9.2-rc2?

[Avital Oliver]

Arg! Again. Yes. Sorry:

    meteor remove iron:router

    meteor update --release 0.9.1-rc3

    meteor add iron:rou...@0.9.2-rc2

--

You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.
For more options, visit https://groups.google.com/d/optout.

[Willy Kuo]

Hi,

I found that most of the UI things have been replaced by Blaze. And there's also a back compatible setting UI = Blaze.

Will we also change UI.dynamic to Blaze.dynamic? Thanks

[Willy Kuo]

Hi,

When I render a view by Blaze.renderWithData. And setup a event to remove the view when clicking a cancel button.

I need to remove the parent view of Blaze.currentView since we add Blaze.with between the parent dom and the template view itself.

i.e.

Template.test1.events({
  'click .cancel-button': function(){
    Blaze.remove(  Blaze.currentView.parentView );
  })
});

Does it make sense? I thought I should remove Blaze.currentView but not its parentView

On Friday, August 29, 2014 12:38:15 PM UTC+8, Avital Oliver wrote:

[David Greenspan]

Willy,

Interesting observation.  What happened when you only removed Blaze.currentView?

This code is correct -- though possibly not future-proof.  Ideally, you would call Blaze.remove on the View returned from Blaze.render.  I admit I hadn't thought of this case, though.  It's also not ideal because it won't work if the template is rendered not-with-data.  We plan to improve the situation around programmatically inserting and removing templates after 1.0.

A messier but more correct version of the code would only use parentView if its `__isTemplateWith` property is true.

-- David

[Willy Kuo]

Hi David,

In my case, nothing will be removed if i do 

Blaze.remove( Blaze.currentView )

[Gadi Cohen]

Hey, sorry, I haven't had a chance to play with the rc's yet, but I did just take a quick peak at the source :>  It seems like you're deprecating calling Blaze.Render without a parent element.  This has implications for apps/packages that use Blaze but don't render to the DOM.  Maybe famous-views is the only example for now :)

[Morten Henriksen]

Hi guys, I've been working quite a bit on merging packages to 0.9.1 - one feature request:

I'm getting an error like:

Figuring out the best package versions to use. This may take a moment.

Could not resolve the specified constraints for this project:

Error: conflict: mini...@1.0.2 vs 1.0.

So I guess thats ok - but could it be just a bit more verbose about what packages that conflict (what packages/app that got conflicting dependencies) - so far its a needle in a haystack :)

[Jim Biggs]

Hello,

Upgrading to Meteor 0.9.1 broke my app. My templates and other items are returning errors of being "undefined". I'm pretty sure it has to do with iron:router. I followed the instructions for removing and adding iron:rou...@0.9.2-rc2, but I get the following error when issuing the command...

$meteor add iron:rou...@0.9.2-rc2

Could not satisfy all the specified constraints:

Error: conflict: de...@1.0.2-rc1 vs 1.0.2

 

My app was working perfectly under Meteor 0.9.0

Thoughts?

Thanks... Jim

[Jan-Hendrik Mangold]

On Sep 5, 2014, at 10:48, Jim Biggs <onso...@gmail.com> wrote:

$meteor add iron:rou...@0.9.2-rc2

have you tried just 

meteor add iron:router

[Jan-Hendrik Mangold]

On Sep 5, 2014, at 10:48, Jim Biggs <onso...@gmail.com> wrote:

$meteor add iron:rou...@0.9.2-rc2

 meteor --version
Meteor 0.9.1
 meteor show iron:router
Refreshing package metadata. This may take a moment.
Version 0.9.0 : Routing specifically designed for Meteor
Version 0.9.1 : Routing specifically designed for Meteor
Version 0.9.2-rc0 : Routing specifically designed for Meteor
Version 0.9.2-rc2 : Routing specifically designed for Meteor
Version 0.9.3-rc0 : Routing specifically designed for Meteor
Version 0.9.3 : Routing specifically designed for Meteor

Maintained by iron at https://github.com/eventedmind/iron-router.

[David Greenspan]

Hi Gadi, can you be more specific?  What does it mean to not render to the DOM?

Thanks,

David

On Friday, September 5, 2014, Gadi Cohen <gadic...@gmail.com> wrote:

Hey, sorry, I haven't had a chance to play with the rc's yet, but I did just take a quick peak at the source :>  It seems like you're deprecating calling Blaze.Render without a parent element.  This has implications for apps/packages that use Blaze but don't render to the DOM.  Maybe famous-views is the only example for now :)

--

[Jim Biggs]

I removed deps and added tracker. My new error when adding iron:router follows...

meteor add iron:rou...@0.9.2-rc2

Refreshing package metadata. This may take a moment.

Figuring out the best package versions to use. This may take a moment.

Could not satisfy all the specified constraints:

Error: conflict: ej...@1.0.1-rc0 vs 1.0.1

ejson is not in my meteor package list.

[Avital Oliver]

Announcement: 0.9.1 has been released! No need for -rc versions of Meteor or iron:router. To upgrade, run:

    meteor remove iron:router

    meteor update

    meteor add iron:router

Enjoy!

--
You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.
For more options, visit https://groups.google.com/d/optout.

[Jim Biggs]

I just tried "meteor add iron:router" and it worked. I'm now at iron:router version 0.9.3.

However, my app still fails. Below is an excerpt of output from the console:

Uncaught TypeError: Cannot read property 'registerHelper' of undefined roles_client.js:78

Uncaught TypeError: Cannot read property 'Roles' of undefined accounts-admin-ui-bootstrap-3.js?168f6890c863442d6089c32dbf95e05e450dcdbe:22

Uncaught TypeError: undefined is not a function dynamic_template.js:371

Uncaught TypeError: Cannot read property 'prototype' of undefined helpers.js:139

Uncaught TypeError: undefined is not a function router.js:61

Uncaught TypeError: Cannot read property 'RouteController' of undefined fast-render.js?85ee31c215be8703a3dea3fbe233d96b255bc9fc:25

Uncaught Error: There are multiple templates named '__IronDefaultLayout__'. Each template needs a unique name. templating.js:9

Uncaught TypeError: undefined is not a function router.js:61

Uncaught TypeError: Cannot read property 'RouteController' of undefined iron-router-progress.js?2b52a697e5a2fba4ec827721c08cfdd0a5bae508:25

Uncaught TypeError: Cannot read property 'registerHelper' of undefined roles_client.js:74

Uncaught TypeError: Cannot read property 'FastRender' of undefined global-imports.js?91ea697c7a3f3758d8082e108fdaaa3f1c3a9cc9:4

Uncaught ReferenceError: Template is not defined template.dashboard.js?78558f7f42153d605eae23ffe5ef7fb14d1b5272:2

Uncaught ReferenceError: Template is not defined template.home.js?d0cfa2ec5e256a968fa1fda41a8cdbe418c1a518:2

Uncaught ReferenceError: Template is not defined template.layout.js?65bb09f89c13cccf2898311937a3e1f17be7bddb:2

Uncaught ReferenceError: Template is not defined template.search.js?3ae92253f6098449836762af5692927f754365ef:2

Uncaught ReferenceError: Template is not defined 

I'm really at a loss. I've never experienced this much difficulty updating Meteor -- even with the rc-releases.

Thanks... Jim

[Jan-Hendrik Mangold]

roles in its current version is incompatible

https://github.com/alanning/meteor-roles/issues/53

[Adrian Lanning]

How do we define a range for the supported package versions?

We are trying very hard to keep the `roles` package backwards compatible without maintaining two codebases.  The issue is that the roles package supports both blaze@1 and blaze@2 but it seems we have to specify one or the other in `package.js` which means we can support all Meteor prior to 0.9.0, and either Meteor 0.9.0 or 0.9.1, but not both (which would just be silly).

Alternately, we could leave off the specific version info for blaze if there is a way to tell Meteor to use the same Meteor Version as the app. For example,

if (api.versionsFrom) {
  api.versionsFrom("METEOR@<Whatever the app is using>");
  api.use(['blaze'], 'client', {weak: true});
}

[Andrew Mao]

Does the addition of organizations come with renaming capabilities? If not, what's the best way to rename packages?

On Friday, September 5, 2014 4:19:02 PM UTC-4, Valerio Santinelli wrote:

It looks like there's a bug with the new package management system btw.. running meteor list gives a list of packages with available updates but meteor update does nothing.

More here: https://github.com/meteor/meteor/issues/2526

Valerio

[Paul Wujek]

meteor update seems to have automatically upgraded iron-router to 0.9.3 without the need for deleting it in advance.

  downloading iron:router at version 0.9.3 ...  done
  upgraded iron:router from version 0.9.1 to version 0.9.3

[Gadi Cohen]

In case anyone else is interested, I'm moving this conversation to a separate thread:

[meteor-core] Blaze rendering not tied to the DOM

[Adrian Lanning]

This is getting ridiculous.  

`api.versionsFrom` as it is now is an anti-pattern and we also can't specify a range for specific packages.

What should package authors do about this?

For the `roles` package I can release a new version but that means that the current version, 1.2.12, will be the last version that supports Meteor 0.9.0 and 0.9.0.1.  Version 1.2.13 and onwards will support pre-0.9.0 and 0.9.1+ but not those two.

Wow...

...now what happens with packages that use `roles` as a dependency?  If they specify `roles@1` which should be safe ("Now that we're using SEMVER, this is safe, right?") people who use 0.9.0 get their apps broken with the `roles` package as the "culprit".

Here is an example repo for people to try these things out with:
https://github.com/alanning/meteor-test-versionsFrom

MDG, please help

[Adrian Lanning]

FYI, `alanning:roles` v1.2.13 is out which provides explicit support for Meteor 0.9.1 (and 0.9.1.1).

We're seeing some weird behavior with Meteor 0.9.1 where an older, incompatible version of the roles package is being pulled down, but updating to Meteor 0.9.1.1 seems to resolve it.

I believe you can pull down both the latest Meteor and roles by running `meteor update`.  Or if you prefer you can run: `meteor remove alanning:roles` followed by `meteor add alanning:roles` and that should work with Meteor 0.9.1.1.

To see which package versions you are using, run `meteor list` in your app directory.

Note: prior versions of Meteor will still use roles v1.2.12 - there is no functional difference between roles v1.2.11, v1.2.12, and v1.2.13.

Package authors, please consider weighing in with your view on better supporting backwards compatibility here: https://github.com/meteor/meteor/issues/2531

[Arunoda Susiripala]

There is no way to specify a range. Only the minimal version. 

If you omit versionsFrom, you need to handcode versions. 

Having said that, we need better versioning support for pre-releases. 

--
You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.
For more options, visit https://groups.google.com/d/optout.

--

---

Arunoda Susiripala

I curate Meteor Weekly - Check it out!

[Adrian Lanning]

That is what I originally thought but the reality is that `api.versionsFrom` is not specifying a minimal version but is instead specifying a Meteor version to pull core packages from. 

Consider this example: `api.versionsFrom('MET...@0.9.0')`

The way it works now is:

  "Use the core packages from Meteor version 0.9.0"  <= This is a problem!

... rather than:

  "support Meteor versions from 0.9.0 up"  <=  Would be ok.


You can try this yourself using this example repo:  

  https://github.com/alanning/meteor-test-versionsFrom

Change the code in "packages/roles/package.js" to this:

    api.versionsFrom('MET...@0.9.0');

    api.use(['blaze'], 'client');

And change ".meteor/release" to this:

  MET...@0.9.1.1

You will get the following error:

  Could not resolve the specified constraints for this project:

  Error: conflict: bl...@1.0.3 vs 2.0.0

The current state of the world requires some packages to maintain a different codebase for each Meteor release, which is not reasonable. 

Please follow this issue here and feel free to weigh in with your thoughts: 
  https://github.com/meteor/meteor/issues/2531

[Gadi Cohen]

I think it's saying "Use the core packages from Meteor version 0.9.0" that are still API compatible.

Blaze did indeed get a breaking change... e.g. the version of famous-views that relied on versionsFrom("MET...@0.9.0") would have stopped working in 0.9.1 because of the difference in the Blaze API.  So that behaviour, in this case, is good.

Of course, roles and other packages would have ("could have") continued to work without a problem.  So that behaviour, in this case, is bad.

Since it can go both ways, maybe it is better to depend on actual package versions rather than Meteor releases, of course as pointed out above, we still have other issues to solve for that.

On Sunday, September 7, 2014 5:05:10 PM UTC+3, Adrian Lanning wrote:

That is what I originally thought but the reality is that `api.versionsFrom` is not specifying a minimal version but is instead specifying a Meteor version to pull core packages from. 

Consider this example: `api.versionsFrom('METEOR@0.9.0')`

[Oli Evans]

Hey that's a big +1 on being able to migrate a user account to an org account.

We're using  london: as the common prefix for packages from the Meteor London crew, but right now it's a user account.

O!

On Friday, 29 August 2014 18:57:33 UTC+1, Emily Stark wrote:

Hi Morten -- that's correct, users and organizations are in the same namespace. We'll be working out something soon (probably next week) for users that should be converted into organizations.

[Dave Workman]

is Blaze.getCurrentData now Blaze.getData? I see nothing about getCurrentData mentioned in the release notes, but my app is now complaining Blaze.getCurrentData is not defined in 0.9.1

[Avital Oliver]

Dave, yup. http://docs.meteor.com/#blaze_getdata

--
You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.

For more options, visit https://groups.google.com/d/optout.

--

[Andrew Mao]

Dave Workman: I just mentioned this in https://github.com/meteor/meteor/pull/2538