[FEATURE] SASS/Coffeescript Support about live-server HOT 5 CLOSED

👍 @famousgarkin, I agree. Those asset tools should be run separately to live-server.

For example, my working setup involves SASS and I run node-sass via CLI to meet my needs. When I make changes, my sass is compiled into css, which triggers a nice reload by live-server.

Tips for anyone using node-sass in combination with live-server:

1. Always install live-server and node-sass as local dev dependencies to your project. This ensures you'll always have these tools frozen and stable for your project:

   $ npm install live-server node-sass --save-dev

2. Running node-sass (assuming input of css/sass/style.sass, and output of css/style.css):

   $ ./node_modules/.bin/node-sass -w css/sass/style.scss -o css --source-map=true --output-style=compressed

   Note: node-sass catches changes from within the @import file calls, which is great.

3. Running live-server:

   $ ./node_modules/.bin/live-server --no-browser --ignore=css/sass,css/style.css.map

   Note: live-server reloads when your sass files changes, but this isn't ideal. It should ignore those changes until node-sass finishes compiling the css/style.css file.

4. To bring it all together, you can add a clean custom script to your package.json file:

   {
     // ... package.json metadata ...
     "scripts": {
       "dev-mode" : "node-sass -w css/sass/style.scss -o css --source-map=true --output-style=compressed & live-server --no-browser --ignore=css/sass,css/style.css.map"
     }
   }

   Then to run both tools, it's just npm run-script dev-mode!

from live-server.

Interesting idea. However, this project was born from my own needs and as I don't use Sass (or Less) nor CoffeeScript, I don't see myself working on this any time soon. I'm open to contributions though. :)

One thing I'm slightly worried is that after implementation the next issue would be either adding more directory name alternatives and/or adding configuration in order to make it work when someone else uses different conventions. That would make it less "zero-conf" and make it more complex. Not a huge deal though.

from live-server.

There's enough options available to watch and rebuild assets in parallel with running live server. Please keep it slim and focused, don't turn into another Grunt/Gulp/webpack/whatever do-it-all plugin and configuration craziness.

from live-server.

@famousgarkin +1

from live-server.

(-1) @famousgarkin +1
Just run the live-server at the same time as whatever compilers/watchers/build tools.

from live-server.