Shouldn't be a gulp plugin

[sindresorhus]

Users should instead just use gulp-spawn or ChildProcess.spawn() directly.

[MasseGuillaume]

@sindresorhus why?

[sindresorhus]

Your plugin should not do something that can be done easily with an existing node module

https://github.com/gulpjs/gulp/blob/master/docs/writing-a-plugin/guidelines.md

[revathskumar]

@sindresorhus noted. This was an experimental one. my first gulp plugin.

[natecox]

Gulp plugins are also supposed to do only one thing. Using a plugin to simply spawn child tasks to do any number of things also breaks the guidelines. This plugin achieves the goal of compiling dart to JavaScript and shouldn't be shot down, otherwise every other plugin to compile a language based on a third party compiler is also wrong.

[sindresorhus]

@natecox it has nothing to do it being spawned, but rather that gulp plugins should only work on the in-memory file contents, not fs paths. This plugins uses file.path, which means any plugins coming before it is moot.

[sindresorhus]

ping