search

nate-strauser / wework

We Work Meteor, a job board and developer directory for Meteor specific work
https://www.weworkmeteor.com
MIT License
288 stars 145 forks source link

Freeze mrt packages or update to Blaze #5

Closed paulmolluzzo closed 10 years ago

paulmolluzzo commented 10 years ago

I was trying to tackle adding an RSS feed and came across an issue that is going to block future updates that rely on a new mrt package. In meteor v.0.8.0 there's the new Blaze templating engine, and a number of packages in this project (iron-router for one) have made updates that now depend on Blaze. As a result, if you try to add a new mrt package, you'll get errors like this when trying to run mrt or meteor.

Two solutions that I can think of:

  1. Update the project to meteor 0.8.0 and move all the templates over to the Blaze syntax. I don't know how deep this goes, but it's probably a lot of work.
  2. Freeze all the included packages at the currently used version. Basicaly, in the smart.json there are no versions specified for any of the packages, so they're going to use the latest version whenever requested.
nate-strauser commented 10 years ago

i'm in the process up upgrading to blaze now - just a couple tweaks remaining, should be done and deployed in a day or two -- i just pushed the still partially broken version up to master

On Tue, Apr 1, 2014 at 12:46 PM, Paul Molluzzo notifications@github.comwrote:

I was trying to tackle adding an RSS feed and came across an issue that is going to block future updates that rely on a new mrt package. In meteor v.0.8.0 there's the new Blaze templating engine, and a number of packages in this project (iron-router for one) have made updates that now depend on Blaze. As a result, if you try to add a new mrt package, you'll get errors like this http://pastebin.com/W9LCe7rK when trying to run mrt or meteor.

Two solutions that I can think of:

  1. Update the project to meteor 0.8.0 and move all the templates over to the Blaze syntax. I don't know how deep this goes, but it's probably a lot of work.
  2. Freeze all the included packages at the currently used version. Basicaly, in the smart.json there are no versions specified for any of the packages, so they're going to use the latest version whenever requested.

Reply to this email directly or view it on GitHubhttps://github.com/nate-strauser/wework/issues/5 .

nate-strauser commented 10 years ago

upgrade to blaze complete - wasnt too bad actually - new version deployed