4 ms·
I think I'm missing something. I see how this would be great when it's build time but during development I don't want to have to keep running build commands eac
by bpatrianakos 12y ago
I think I'm missing something. I see how this would be great when it's build time but during development I don't want to have to keep running build commands each time I want to use a new package I'm development. Using Grunt and Bower may be a little time consuming up front but once things are set up its very easy to keep a separate Dev and prod environment in sync between different contributors. I only see the value at build time with Duo which is why I'm sure I missed something.
- michaelmior 12y agoDon't you already have to run some command to install the new package anyway? Not really sure I see how this is different in that respect.
- TheHydroImpulse 12y agoYou inherently need a build step when working with remote dependencies or even any dependency. Especially when you're working with various assets like templates, css, images, etc... Typically, let's say for an app, you'll run a watcher which will trigger the builder, so you can just spin it up and leave it alone. For smaller components that are meant for consumption, a simple Makefile is more than enough and running the command isn't too terribly bad.
- tjsix 12y agoIt looks like the cli utility has a built in watch flag that can be passed to automatically rebuild on changes
- Kiro 12y agoYou need to run a build script for Browserify as well, which IMO everyone who is using Bower/RequireJS should switch to.
- davej 12y agoI imagine it would possible to wire up a simple watcher in gulp/grunt that would do this automatically.