one-gulp
[WIP] a ready to use set of gulp tasks
install
If your're starting a new project, you just need to run this :
npm install gulp one-gulp --save
This will install gulp
and the one-gulp
node module. If you don't have a gulpfile.js
in your project, it will generate one with the minimum configuration.
init
If you're already using gulp, you need to install the one-gulp
node module by running this :
npm install one-gulp --save
and then you'll be able to init one-gulp
with this code :
var gulp = one = ; one;
The one.init()
function adds several tasks to your gulp :
- serve
- watch
- writeToDev
- writeToProd
- browserSync
- graph
config options
src
tmp
dest
connectPort
browserSyncPort
bindHost
sortDeps // relative to src
Remote debugging
Using browser's tools
Chrome, Firefox, Opera and Safari provide remote debugging for their latest desktop and mobile browsers :
- Remote Debugging on Android with Chrome
- Debugging Firefox for Android with WebIDE
- Remote Debugging with Opera Dragonfly
- Enable Remote Debugging with Safari Web Inspector in iOS 6
Using weinre
If you need to remote debug older versions of the above browsers, Internet Explorer or a WebView, you'll have to use weinre.
one-gulp uses BrowserSync, so weinre is already installed. You just need to add a target script in your pages and enable the debug interface.
Manual target script injection
If you want weinre to work, you can manually add a target script like this in your pages :
Automatic target script injection
You can also set options.injectWeinreSnippet
to true
to automatically inject the weinre target script in your pages. This will only work on the BrowserSync port.
Enable the debugger
By default, after starting the servers, weinre is disabled. To enable it, just follow these two steps :
- Open http://[your-local-ip]:[browser-sync-conf-port]/remote-debug and enable Remote Debugger (weinre).
- Click on the Access remote debugger (opens in a new tab).