-
Notifications
You must be signed in to change notification settings - Fork 5
Add --watch flag to serve command #23
Comments
thinking about this a bit more - I think we actually are in luck of sorts. most/all of the watches that come with editions are defined from the take this snippet from the edition-node-gulp
all this really equates to is "hey PL, build again when something you care about and already use changes" the css is one place where, in my mind, we can optimize things by directly injecting via BS. again from the gulpfile:
we can do that on behalf of users too I think. anyone that wants to do something with their asset pipeline still can, knowing that once changes hit our watched directories, PL takes over if need be we might need to be careful about this snippet, however, which supports watching whichever template extensions a user has engines for
I think this can likely be internalized too I will open a different issue discussing remaining browsersync server options to consider. |
Thanks … this sounds great and mitigates a lot of boilerplate |
Fixed via c696a6a |
This is a must-have for all PatternLab power users, so that they can specify their own paths to watch
The text was updated successfully, but these errors were encountered: