03:12 <bobthecow> nanoc can only see if the main file changed, it can't tell that the main file depends on all those // require'd files.

05:44 <ddfreyne> Yeah. dependency tracking is hard.

05:45 <ddfreyne> I wish libraries that have includes all had APIs for finding includes

05:54 <travis-ci> [travis-ci] nanoc/nanoc/old-4.x 500b8fd Denis Defreyne: The build has errored.

08:27 <guardian> o/

13:10 <smaboshe> Hello! I'm experimenting with the Bower package manager (http://bower.io/) to manage dependencies for a nanoc 3.6.11 project. Is there a recommended way to use Bower with a nanoc project?

15:32 <VitamineD> hard to say… I'd probably manage the bower file as a nanoc item, but run bower itself as part of the deploy

15:34 <smaboshe> Thanks. So ignore nanoc can basically contents of bower_components?

15:38 <VitamineD> you don't seem to be thread safe, your words show up in random order :p

15:39 <VitamineD> but yes, I don't see the point of handling bower-managed files with nanoc

15:39 <smaboshe> Thanks, I'll try that (hopefully, in the right order ...).

15:40 <VitamineD> I'm not sure if you can have compile steps that generate more than one file

15:40 <VitamineD> doubt it, actually

16:12 <smaboshe> No, I don't think so either. I'm looking at using the data_sources option with 'passthrough' to copy over the bower components.