-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for assemble 0.7.x #35
Comments
@grouchal Thanks for the issue! If you're reporting a bug, please be sure to include:
|
+1 on this. I use Assemble on both Grunt and Gulp projects, and would like to keep them in sync if possible (having already moved onto 0.7 by using Assemble direct with Gulp). Any idea when this is likely to be updated? |
already started work on it. Not sure how long it will take, I'll let you know as soon as I or @doowb make more progress |
Great – thanks for the update 👍 |
@jonschlinkert Any news here? Would love to see an update for Grunt. |
@jonschlinkert Thanks! I've seen it already. When will you release it? |
@jonschlinkert I've used your latest develop (https://codeload.github.com/assemble/grunt-assemble/tar.gz/a824b27eba5f00797452cf03854911e50e457694) but Also the interactive question |
Since assemble v0.6.0 and up can run any engine, it wouldn't make sense to add any particular engine as a dep. We should probably just remove the prompt and throw an error. Fwiw, I personally thought the prompt was a nice experience, it worked well for me - we also do something similar with gulp and generate. But I can see how it might be hard to make it work well consistently. In any case it's pretty easy to add engines: // where `hbs` is the file extension to match
app.engine('hbs', require('engine-handlebars')); |
Any idea when this is coming
The text was updated successfully, but these errors were encountered: