@richiardiandrea I spent some time trying to take your lessc
task and integrate perun's file watching, but I don't think it'll be very clean as long as compile-less-file!
depends on the npm/exec
task. Perun isn't design to require a fileset for its rendering functions, and so the way that compile-less-file!
invokes npm/exec
kind of outside the main task chain makes it difficult. I think I might take this and implement something like lessc
in Perun itself though.
@bhagany first of all thanks 😄
second, I am using npm/exec
for side effects only but I am passing things explicitely
I should maybe refactor more so that I don't have any dependency on the fileset
I think there'd have to be a non-task way of executing npm
yeah...probably actually shelling out is a better option
interesting, that's what I'd do with Perun (we use conch
), but we'd lose the handy npm install that npm/exec
does
npm/exec
uses the fileset because of the :include
option only (I am checking)...
yes, that's how I read it
er, well, I guess it still has to return the fileset, even in the absence of :include
yes one way or another you'll need to return the fileset but it is true that my task could be simplified with conch
npm/exec
puts some sugar around npm
binary detection basically
right. Perun's pattern is just to say "you have to have this external package installed" and then assume that it is. degree9's way of handling npm is nicer, and I like it.
I think also that he has some improvement coming out
interesting, I'll keep an eye on it
😄
but feel free to throw stuff at me in case you want to try it out...I have a setup with Semantic UI going
btw is there a perun SNAPSHOT
version with the latest changes by any chance?
an a preview of the website for this #perun 😄 you guys deserve it given the hard work you put into it 😄 http://andrearichiardi.com
nice site!
I'm not sure about the latest snapshot... @podviaznikov does those
when your officially launch your site, feel free to submit a PR to include it in Perun's README
Ok thanks! I see there are a couple of problems here and there ;)