Exact workflow with sass:dev VS sass:prod using last default starterkit (GULP/NODE.js) [#2581937]

Hi all,

I'm an absolute newbie in GULP/LIBSASS/NODE.js paradigm, so I have the following question:

What is the exact workflow to use sass:dev VS sass:prod within gulpfile.js ?

It is intended to use "gulp sass:prod" at very last operation before deploy to prod?
If yes: how can this be reconciled with GIT workflow?
What is and what it is used for the following piece of code in package.json?

"scripts": {
    "sass:dev": "./node_modules/.bin/gulp",
    "sass:prod": "./node_modules/.bin/gulp sass:prod"
  },

Thank you very much for helping me.

Comments

Comment #1

7 October 2015 at 14:57

MXT created an issue. See original summary.

Comment #2

BenMirkhah CreditAttribution: BenMirkhah commented 13 October 2015 at 20:06

During dev your build process may include extra debug info like source-maps, while for production you may want to minify / uglify to save on file size, as far as git workflow, on your dev work branch you commit code compiled using the dev setting, once development is over and prior to merging into master you build using the production settings, test it, merge into master, tag and deploy.