Grunt workflow

[KittyGiraudel]

Or Gulp. Whatever.

Now that we have quite a few things going on (Sass watching, JSHint...), perhaps having a more powerful than Make, task-based workflow wouldn't be such a bad idea, right?

@valeriangalliat, @FWeinb, what do you say?

[valeriangalliat]

Well I don't know, I like makefiles, especially for something as straightforward as running commands — and I usually use inotifywait in a shell loop for "watch" tasks... but Grunt or Gulp is a good solution to write something more portable.

EDIT: I just saw that you can run sass --watch. I don't know which tools they use for this but this removes the inotifywaity portability problem (but well... a makefile isn't still the best solution for Windows, and I'd prefer Grunt/Gulp than using CMake).

[KittyGiraudel]

So, @pascalduez seems on fire to build the Gruntfile and shit and stuff. @FWeinb, if you're okay, we do this.

[FWeinb]

Let's do it.

[KittyGiraudel]

@pascalduez, your move.

[FWeinb]

Do we want to this for 1.0? Would be good because than we could run tests and integrate with travis.

[pascalduez]

Currently making it my priority.

[KittyGiraudel]

Tagged for 1.0. We won't go live until we have a clean workflow, including automated tests.

[KittyGiraudel]

$ grunt watch
Running "watch" task
Waiting...
>> File "view\templates\layouts\base.html.swig" changed.
Running "compile" task
Fatal error: spawn ENOENT


Execution Time (2014-07-08 11:15:00 UTC)
loading tasks  70ms  ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ 91%
compile         6ms  ■■■■ 8%
Total 77ms

Completed in 0.853s at Tue Jul 08 2014 13:15:00 GMT+0200 (Paris, Madrid (heure d’été)) - Waiting...

Note: Fatal error: spawn ENOENT.

$ grunt dist
Running "browserSync:dist" (browserSync) task

Running "watch" task
Waiting...
[BS] Local: >>> http://localhost:3000
[BS] External: >>> http://10.0.1.94:3000
[BS] Serving files from: examples/dist

[BS] Watching files...
>> File "view\templates\includes\sidebar.html.swig" changed.
Running "compile" task
Fatal error: spawn ENOENT


Execution Time (2014-07-08 11:45:42 UTC)
loading tasks  70ms  ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ 92%
compile         5ms  ■■■■ 7%
Total 76ms

Completed in 0.843s at Tue Jul 08 2014 13:45:42 GMT+0200 (Paris, Madrid (heure d’été)) - Waiting...

Note: Fatal error: spawn ENOENT.

Execution Time (2014-07-08 11:49:03 UTC)
loading tasks   71ms  ■■■■■■ 11%
sass:view      573ms  ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ 89%
Total 645ms

Completed in 1.488s at Tue Jul 08 2014 13:49:04 GMT+0200 (Paris, Madrid (heure d’été)) - Waiting...
[BS] File Changed: prism.min.js
[BS] Reloading all connected browsers...
Error: EPERM, stat 'c:\Users\DEV-07\Documents\Sources\SassDoc\examples\dist\assets\css\main.css'
>> File "view\scss\partials\_map.scss" changed.
Error: EPERM, stat 'c:\Users\DEV-07\Documents\Sources\SassDoc\examples\dist\assets\css\main.css'
Running "sass:view" (sass) task
File view/assets/css/main.css created.

Done, without errors.

Note: Error: EPERM, stat 'c:\Users\DEV-07\Documents\Sources\SassDoc\examples\dist\assets\css\main.css'

[pascalduez]

No issue here, I suspect a Windows thing. Investigating.

[FWeinb]

Related issue: nodejs/node-v0.x-archive#4337

[KittyGiraudel]

Merged in 1.0.0-rc.12.

[pascalduez]

The ENOENT should be fixed, but there is still the EPERM I guess. On Win, of course.