Different command to build for production?

[johnpez]

Hi, Thanks for this nice platform...I've used it on a couple of projects now, it's my first intro into gulp, browsersync, and a few other tools here.

Maybe I'm missing something simple but I didn't see this covered in your docs: is there a different command to build for production?

The main issue I've noticed is that the scripts.min.css file includes, by default, the sourcemaps which (more than?) doubles the size of the file. I'm not sure what the intended usage is, if I should be running "gulp" with other arguments in order to build the site for production, if there are other reasons for doing so, etc.

Can you please share your strategy here? Thanks!

[AsafAgranat]

Fastshell keeps simple by having only few tasks in its gulpfile. Build is not a separate process. Instead, every time you change files it compiles the necessary assets into the 'app' folder. Your 'app' folder is then your ongoing build folder. I use fastshell often for quickly getting up and running with prototypes. I always end up expanding the gulp file to watch more file locations. Its a good starter for learning gulp and adding tasks as you go. CSS source maps help browsers know how to map the compiled and minified css to your source scss, helping debugging. If you inspect your code source you can see it tells you which files are associated with specific styles. You can easily remove the pipe to create source maps in the gulpfile, under the 'css' task.

[johnpez]

Thanks for the response, just what I was looking for =)