{"action":"opened","issue":{"url":"https://api.github.com/repos/haydenbleasel/gulp-favicons/issues/2","labels_url":"https://api.github.com/repos/haydenbleasel/gulp-favicons/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/haydenbleasel/gulp-favicons/issues/2/comments","events_url":"https://api.github.com/repos/haydenbleasel/gulp-favicons/issues/2/events","html_url":"https://github.com/haydenbleasel/gulp-favicons/issues/2","id":56085627,"number":2,"title":"call syntax seems inverted","user":{"login":"jessaustin","id":295056,"avatar_url":"https://avatars.githubusercontent.com/u/295056?v=3","gravatar_id":"","url":"https://api.github.com/users/jessaustin","html_url":"https://github.com/jessaustin","followers_url":"https://api.github.com/users/jessaustin/followers","following_url":"https://api.github.com/users/jessaustin/following{/other_user}","gists_url":"https://api.github.com/users/jessaustin/gists{/gist_id}","starred_url":"https://api.github.com/users/jessaustin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jessaustin/subscriptions","organizations_url":"https://api.github.com/users/jessaustin/orgs","repos_url":"https://api.github.com/users/jessaustin/repos","events_url":"https://api.github.com/users/jessaustin/events{/privacy}","received_events_url":"https://api.github.com/users/jessaustin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-30T21:15:00Z","updated_at":"2015-01-30T21:15:00Z","closed_at":null,"body":"I've tried to integrate `gulp-favicons` into my `gulpfile`, and I've just about given up in favor of just using `favicons` directly. I think the reason is that `gulp-favicons` is mostly about creating favicons, yet it's called as if it were mostly about writing `<link rel= >` tags. What would make sense to me would be something like:\r\n```javascript\r\ndata = require('gulp-data') # etc.\r\ngulp.task('favicons', function() {\r\n    gulp.src(['src/small-favicon.png', 'src/large-favicon.png'])\r\n        .pipe(favicons({settings: { background: '#1d1d1d' }})\r\n        .pipe(gulp.dest('./'));\r\n});\r\ngulp.task('html', ['favicons'], function() {\r\n    gulp.src('src/**/*.jade')\r\n        .pipe(data(function() {\r\n            return {linkRels: favicons.linkRels()};\r\n        }))\r\n        .pipe(jade())\r\n        .pipe(gulp.dest('./'));\r\n});\r\n```\r\nThe point is that it's good to keep the favicons in the stream, rather than writing them to disk like `grunt` would. One might want to do something to the original image before passing it to `gulp-favicons`, or one might want to transform the generated favicons somehow.\r\n\r\nAnother point (and frankly what started me on this) is that `gulp-favicons` should not be in the templating business. It's great that it produces a sequence of `<link rel= >` tags, but it should be willing to just pass that string along rather than insisting on writing it to disk or inserting it into an already-existing stream. Let `gulp-jade` et al. worry about that.\r\n\r\nI'll write a patch if this doesn't sound like a terrible idea?"}}