Change ServiceStackVS templates to Gulp
Gulp has got much better friction in the community than Grunt and many people already moved to Gulp completely. ServiceStack SPA templates use Grunt and leverage Gulp packages via grunt-gulp, which seems to be articifial. Wouldn't it be easier just to remove Grunt at all and make everything with Gulp instead?
All Single Page App Templates have now been modernized in the latest v1.0.22 update:
https://github.com/ServiceStack/ServiceStack/blob/master/docs/2016/servicestackvs/v1.0.22.md
They now use Gulp and JSPM and both React Templates are now pre-configured with TypeScript
-
Alexey Zimarev commented
Cool!
-
Darren Reid commented
This can be closed off now as all templates in ServiceStackVS since 1.0.22 now use Gulp only. Grunt and Bower use has been removed to make things simpler with just the use of 1 front end build tool.
the run-sequence packaged was used for orchestration of tasks as Gulp still doesn't have a built in way to easily create sequences, but this package fills that gap nicely.
-
Darren Reid commented
Thanks for the feedback. It would make things simpler to just have the one which is why grunt-gulp was used over having both a gruntfile.js and gulpfile.js.
Grunt was used as the host as it has simpler task orchestration. Gulps focus on "maximum concurrency" lends itself to watch tasks eg, compile on save rather than packaging/staging. Orchestrating and combining sequential and parallel tasks at the time of dev wasn't a good fit for what the SPA templates do, eg not used as a part of the developer workflow/iterations.
It's worth investigating again as I agree Gulp's tools and modules are powerful and concise. Thanks again.