See the gulp introduction slideshow for a rundown on how gulp came to be.
gulp is always lowercase. The only exception is in the gulp logo where gulp is capitalized.
gulp plugins always include the gulpplugin
keyword. Search gulp plugins or view all plugins.
See the Writing a gulp plugin wiki page for guidelines and an example to get you started.
Probably. Ask yourself:
- Is my plugin doing something that other plugins may need to do?
- If so, that piece of functionality should be a separate plugin. Check if it already exists on npm.
- Is my plugin doing two, completely different things based on a configuration option?
- If so, it may serve the community better to release it as two separate plugins
- If the two tasks are different, but very closely related, it's probably OK
Always use \n
to prevent diff issues between operating systems.
I installed gulp as a dependency from package.json file by running npm install
but I keep getting command not found
whenever I try running a gulp command, why doesn't it work?
Upon installing gulp as a project dependency, you need to add that to your PATH environment variable so that when you run a command, the system can find it. An easy solution is to install gulp globally, so that its binaries end up in your PATH environment variable. To install gulp globally, use the command npm install gulp-cli -g
gulp updates can be found on the following twitters:
Yes, come chat with us on Gitter.