You're right, the CLI currently works independently of gulp/grunt/other 
build tools. And as a CLI, it's configuration is limited by how it is 
called and the number of flags it can reasonably support. We'd like the CLI 
to support everyone (from beginner to advanced) so in the coming weeks we 
will be looking into supporting more complex configurations and build 
processes via gulp, grunt, or similar.

If you're currently set up and running with gulp, I'd recommend you hang 
tight for few more weeks until we hopefully have a better idea of what that 
will look like.


On Tuesday, May 31, 2016 at 4:42:44 PM UTC-7, Carlos Araya wrote:
>
> I think these are two different tools.
>
> The Polymer CLI wraps around some of the older available tools like 
> polyserve and polylint. 
>
> Gulp, on the other hand takes care of the build stage processes like 
> SASS/CSS processing, Image minimization, vulcanization and other related 
> build steps.  If you run these tools from Gulp there's no real need to 
> change form one to the other 
>
> Where do you see the CLI replacing  gulp? 
>
> On Monday, May 30, 2016 at 7:46:56 PM UTC-7, Hans Dulimarta wrote:
>>
>> I've been using "gulp" + "yo polymer" (Thanks Rob) to manage my Polymer 
>> app, but after following all the updates post Google IO 2016, the Polymer 
>> team is now heading in a different direction that seems to encourage more 
>> use of polymer-cli than gulp. The two utilities expect different directory 
>> structure. I'd like to hear input whether I should stick with "gulp" or 
>> port my app to "polymer-cli". Where can I find instructions to port my 
>> gulp-based project to polymer-cli?
>>
>

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/23b41878-6020-41c1-8da7-d1b4eb436ee4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to