Closed erik-sb closed 9 years ago
Having the same issue on #200. (with a bit more details)
An easy temporary fix is to add a dependency to emblem 0.3.18 in your package.json
.
@tmosmant thanks, that's actually what I ended up doing, 0.3.18 seems to be working fine. Not sure what's actually triggering this. Sounds like @BenjaminN thinks it has something do do with components, which we're using pretty extensively so that would make sense.
0.3.19 should have been 0.4.0 because it depends on Handlebars 2. 0.3.18 is the last version dependent on Handlebars 1
Thanks @machty, appreciate the response.
Just so you know @erik-sb, I forked gulp-ember-emblem so it can work with the latest EmblemJS. I created a pull request but not sure if @wbyoung is still working on gulp-ember-emblem.
Meanwhile, you can use mine by replacing "gulp-ember-emblem": "0.1.1"
with "gulp-ember-emblem": "git://github.com/BenjaminN/gulp-ember-emblem"
on your package.json
.
It works well with Ember 1.9.1 but doesn't work with the latest EmberJS because EmblemJS doesn't work with HTMLBars yet.
Pulled the update from 0.3.18 to 0.3.19 indirectly via
gulp-ember-emblem
, seeing the following blocking exception being thrown:Downgrading explicitly to 0.3.18 fixes the issue. Saw this brought in handlebars 2.0.0 up from 1.3.x, but I don't have time to delve further into this myself currently. Happy to provide more info if needed.