You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is useful for some situation. F.e. if I processindex.html I don't need to create a stream for a single file
functionbuildProject(options){functiontransform(file,enc,callback){//Transform each .js/.css/.html file}functionflush(callback){//It is more comfortable then use gulp.src(indexPath).pipe(inline()).pipe(someCompileFn())varindexContent=fs.readFileSync(path.join(options.baseUrl,'index.html'));varcompiledIndex=newgutil.File({path: newIndexPath,contents: newBuffer(inline.sync(indexContent,options.baseUrl),'utf8');})this.push(compiledIndex);}returnthrough.obj(transform,flush)}
The text was updated successfully, but these errors were encountered:
Hmm...I think probably I ought to break out an inline module that synchronously inlines an individual file, which gulp-inline may then consume. I'll have to think about this a bit.
It is useful for some situation. F.e. if I process
index.html
I don't need to create a stream for a single fileThe text was updated successfully, but these errors were encountered: