Migrating to Grunt 0.4

[dariocravero]

Hey all,

Grunt 0.4 is almost ready, them team says that the only thing holding its release back are the docs!.

Would it be a good idea to starting the migration?

https://github.com/gruntjs/grunt/wiki/Upgrading-from-0.3-to-0.4

If you agree with that, I can fork branch 0.2.0 and start the upgrade.

Darío

[tbranyen]

Unfortunately there are a lot of breaking changes so it's not entirely straightforward to simply "port over".

I took an initial stab and ended up writing in legacy support for various components that have been removed. Ideally 0.2.0 will be the last version on Grunt 0.3.x.

[dariocravero]

Yes, I was aware of that. It's just that I was trying out things like
grunt-md5 to fingerprint assets and a few others and they wouldn't work on
anything but 0.4 :(

So 0.3.0 could be targeting Grunt 0.4.x, right? I'll take a stab at it, we
may even get some help from the Grunt team since they're in the middle of
the transition :)

Darío

On 7 December 2012 20:17, Tim Branyen notifications@github.com wrote:

Unfortunately there are a lot of breaking changes so it's not entirely
straightforward to simply "port over".

I took an initial stab and ended up writing in legacy support for various
components that have been removed. Ideally 0.2.0 will be the last version
on Grunt 0.3.x.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/89#issuecomment-11150578.

[jonschlinkert]

@tbranyen it already seems like there isn't much choice but to upgrade to start using 0.4. Several of the devdependancies in a couple of my projects are already using "Gruntfile.js" and 0.4. So basically we had to decide to either strip out the "new and improved" Grunt 0.4.0 tasks, create workarounds for the soon-to-be-deprecated ones, or just look for alternatives to the Grunt 0.3.x tasks. Since you can't run both versions of grunt, we decided that the path of least resistance and start transitioning to the new version of Grunt.

Maybe it would be a good idea to create a wip branch for grunt 0.4.0 and put your "inital stab" up there so the community can help with the conversion?

[tkellen]

If you extract the tasks built into bbb and make them regular gruntplugins you'll be 90% of the way there. Then all you have to do is have your users drop the init templates into ~/.grunt-init. They can even just git clone them right in there.

[dariocravero]

@jonschlinkert @tkellen here's what I've been using so far, I'm finishing a project these days and as soon as I do so I'll fork grunt-bbb and start from there.

For convenience, the Gruntfile.js contains everything needed to run the project using grunt itself and not bbb. A part of it will go to backbone-boilerplate, the rest to grunt-bbb.

Of course it lacks some tasks that are on grunt-bbb (e.g.: server, handlebars, etc.) because this version is tailored to work with a particular stack, I'm just removing the unused parts of the config. There's also a requirejs task but it lacks the list and tree helpers because I just didn't need them right now and grunt 0.4 dropped regsiterHelper so I have to take a look at it before implementing it.

A good thing though, I've already included a process to fingerprint (md5 hash) and compress (gzip) released assets which I think it's something that grunt-bbb could get a good use of.

Let me know what you think about it and feel free to start on it if you find that useful :)

[tbranyen]

Just to give some additional information. I've talked with @sindresorhus about potentially merging with Yeoman, but as of right now it is just a premature idea. I'm meeting with @cowboy before I take off for Florida next week to discuss Grunt 0.4 and determining how the project will go on (assuming we don't merge).

Sit tight. I'll post updates as they come. Just need time =)

[dariocravero]

Brilliant! Keep us posted :)

[tbranyen]

I've been working slowly on this since there are a lot of Grunt blockers atm. I've been pushing my progress to the 0.2.0 branch.

[aaronksaunders]

any progress on moving this over to work with yeoman? I saw a deprecated generator projects... wanted to be sure that for now, BBB is standalone

[tbranyen]

ya for now it's still standalone, but I'd love to migrate over if possible.

[hale]

The new yo 1.0 beta docs say to search for generators with npm search yeoman-generator. I take it from this conversation though that there is not yet a working generator for the latest version of yeoman?

[tbranyen]

I checked the BBB generator a few days ago and it wasn't at all accurate. I have a feeling we're moving towards their generators, I just need to take time to see how it works.

[hale]

What would you recommend using for new projects right now, I'm assuming bbb init?

[tbranyen]

Follow the README in https://github.com/tbranyen/backbone-boilerplate mentions you should clone it. I think that's a good way to move forward with backbone boilerplate

[tbranyen]

https://github.com/backbone-boilerplate/generator-bbb