This repository was archived by the owner on Nov 21, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 21, 2018. It is now read-only.
Use browsersync for the development server #302
Description
Currently we use this as a development server:
function startExpress(cb) {
var express = require('express');
var app = express();
app.use(express.static(config.dest));
app.listen(config.server.port, function() {
console.log('Development server running on http://127.0.0.1:'+config.server.port);
cb();
});
}Which works but is definitely not the best way of doing it. Currently the community is more likely leaning towards BrowserSync to fire up development servers. It has many advantages and is compatible with all of our current tooling.
Activity
arthurvr commentedon Apr 3, 2015
I can PR this if y'all like the idea.
Fishrock123 commentedon Apr 6, 2015
Isn't livereload better?
arthurvr commentedon Apr 6, 2015
No. Why do you see them as competitors? These are different tools (although they have some shared functionality). Livereload does not work cross-device, is not that active anymore, doesn't have url URL tunneling, remote inspector, ... It's recommended by Gulp, WSK, generator-webapp, ...
Fishrock123 commentedon Apr 6, 2015
Ah, ok.