No distro-ready build available

[cayuu]

No "ready to use" minified build in the/a repo means that you can't use bower or npm or even git submodule flows to instantly include it in your project without hard linking compiled source. Blegh. This forces one of:

1. Download the .min.js build and include it in your repo
2. CDN/hotlink the minified source link on gh (or put it up on your own)
3. Fork/bower/submodule/etc and run your project through a convoluted* build step

(*) Convoluted because if you're using Grunt in your 'master' project, you'll get all kinds of conflicts with the Grunt.js in the submodule/component/node_modules/ etc.

None of these options are awesome.

Recommended, either:

1. Take a cue from other great projects and include a .min.js version on every release
2. Setup a dedicated npm/bower repo (like Angular does) with the same.

[dharFr]

I just had the same issue today. Can't agree more. 👍

[ksperling]

There hasn't been an official release yet as the project is still in alpha.

The minified files currently live in the gh-pages branch, I take it that's not suitable? It needs to be in gh-pages to be able to serve the sample app via github pages.

I'm finding the need to hand-script all these release process related steps rather tedious... reminds me of Java before Maven came along...

[dmaevsky]

How about just this ?

bower install http://angular-ui.github.com/ui-router/build/angular-ui-states.min.js --save

The drawback is that the version is not frozen in bower.json, but it does not really matter if you include your dependencies into the repository and deploy your app together with them. The advantage, on the other hand, compared to the manual download, is automatic dependencies updates when you need them. Or do I misunderstand something?

[ksperling]

#132