one-gulp/one-gulp

[WIP] a ready to use set of gulp tasks

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 = require('gulp'),
    one = require('one-gulp');

one.init(gulp, {
    // look at options documentation for details
});

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 :

<script src="//[your-local-IP]:[options.weinrePort]/target/target-script-min.js#browsersync"></script>

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 :

1. Open http://[your-local-ip]:[browser-sync-conf-port]/remote-debug and enable Remote Debugger (weinre).
2. Click on the Access remote debugger (opens in a new tab).

one-gulp's Issues

general refactoring

Remove duplications, extracts methods...

task : bump version

release + changelog

tasks : favicon

tasks : sprites

fix inject sort

filterAndSort seems to reorder files in reverse order compared to compilation :-(

TODO :

• check that it works for dev
• check that it works for prod

tests

High severity vulnerability affecting this repo

Hi there,

We noticed that your repo has a high severity vulnerability:

• Regular Expression Denial of Service
• Affected package: negotiator<= 0.6.0

Here is the test report for this repo.
If you’d like to fix this vulnerability, Snyk lets you generate a pull request that recommends the best upgrade path - there’s a link to fix this vulnerability on the test report.

Stay secure :-)

Ben from the Snyk team

tasks : test

tasks : lint

a fresh install does not seem to have gulp-sass correctly

tasks : file revisions

serve font with CORS

right now, fonts aren't served with correct CORS headers and it seems to fail in iframe contexts...

remove/hide first browsersync logs

When calling gulp watch serve, we can see the initial BrowserSync logs...

cache tasks processing on watch

the node_modules folder is too big

I'm starting to have a lot of small projects and the node_modules folder weights around 340mb :-(

add better logs

know what goes through a node and how much time it takes...

watch more than src

documentation

better documentation for various task choices

provide a web interface to see all gulp projects

The idea is to access easily the different exposed gulp projects ports...

allow to bind browser sync only on local network

minifyCss don't follow @import

Maybe use processImport flag.

see https://www.npmjs.com/package/gulp-minify-css

better and more dynamic graph visualizations

be smarter for regeneration of sass, less, jade...

add combined sourcemaps for CSS and prod mode

add changelog support

The big split

dag behaviours and code on one side and recipes and tasks on the other...