If you find Grunt cumbersome to set up, you might want to have a look at assetgraph-builder. The working mantra is that if your browser can understand your page, so should your build system. So you shouldn't need any build system specific annotations in the code, a manifest or configuration file in order to build the page. Sounds like the things you have set up are covering some of the same areas we've already covered pretty well.
It certainly does a lot of things. It's a quite opinionated best practice implementation that does every optimization we could think of. Creating alternate versions that do less isn't that difficult. Most of the build system deals with formatting input arguments correctly, the real magic happens on about 100 lines in lib/transforms/buildProduction, meaning it's quite easy to write an alternate version that does less.
There is angularjs template support, provided you follow the syntax they specify in their documentation.
Comment
If you find Grunt cumbersome to set up, you might want to have a look at assetgraph-builder. The working mantra is that if your browser can understand your page, so should your build system. So you shouldn't need any build system specific annotations in the code, a manifest or configuration file in order to build the page. Sounds like the things you have set up are covering some of the same areas we've already covered pretty well.
Replies
assetgraph-builder looks like it does a millions things. Does it work with angularjs templates?
It certainly does a lot of things. It's a quite opinionated best practice implementation that does every optimization we could think of. Creating alternate versions that do less isn't that difficult. Most of the build system deals with formatting input arguments correctly, the real magic happens on about 100 lines in lib/transforms/buildProduction, meaning it's quite easy to write an alternate version that does less.
There is angularjs template support, provided you follow the syntax they specify in their documentation.