Issue with arge number of files + nested file structure in vendor/bower

[un33k]

With the introduction of the vendor/bower directory, we need to add "vendor/bower" to the watch ignore option.

Ref: testem/testem#301

Details:
I have tested this where I have lot of directories in the vendor/bower directory and if I run "lineman spec", then it fails with error watch: EMFILE. (see Ref)

It seems that testem + fireworm have addressed this issue and bumped the version up.

Solution:

1. Add skipDirEntryPatterns:['node-modules', 'vendor/bower', '.*'] to fireworm config via this module
2. Update testem+fireworm in lineman itself.
3. Update the README to suggest the bower directory be created under the node_modules

Since this module creates 'vendor/bower', it would be nice that it would also handle the testem+firewom config directly.

[un33k]

Pushed a patch to fireworm that also ignores the bower_components directory. This is the default directory created by bower if .bowerrc is not setting a different directory.

airportyh/fireworm#5

Any particular reason for /vendor/bower recommendation in the instruction?

[davidmyersdev]

@un33k, I am also curious about this choice. I opted for the default directory of /bower_components in my installation. Of course, you will have to commit your .bowerrc file if you don't want that to mess up during initial installation.

[jayharris]

The intent was purely to keep all Vendor files together. By using the vendor directory in .bowerrc, everything is in one spot.