-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding in Gulp, Browserify, and Webpack information. #172
Adding in Gulp, Browserify, and Webpack information. #172
Conversation
Not sure how I feel about adding Browserify. I think Gulp makes sense as it's really replaced Grunt. The main reason we've stuck with Grunt is for consistency and the fact that WP still uses it. However, Browserify seems like it's largely being overtaken by Webpack. Thoughts? |
@tlovett1 I've been wrestling with this as well, but wanted to cover my bases. A year ago, I think Browserify might have made sense, but now (in client projects and personal projects) I'm recommending Webpack out of the box. I'm okay dropping that section. |
Browserify is mostly eclipsed by Webpack for our internal tooling uses.
_includes/markdown/Tools.md
Outdated
|
||
[Gulp](http://gulpjs.com/) - Gulp is also a task runner build on Node that offers a similar suite of plugins and solutions to Grunt. The biggest difference is Gulp allows you direct access to the [stream](https://nodejs.org/api/stream.html) of information from your source files and allows you to modify this data directly. | ||
|
||
[Webpack](https://webpack.github.io/) - Webpack is a bundler/task manager - the next generation of JavaScript/CSS development tools. At 10up we are actively building new projects with this library to expand our internal knowledge and find the best use cases. Webpack allows us to combine all of good parts of the above mentioned tools into a single file/command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if webpack is specifically a task runner in the traditional sense, is it? It's a bundler and you can run different file types through it, but you can't really define an arbitrary task to run, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In cases where you use Webpack as a bundler, it generally makes sense to just use plain npm scripts
to manage 'tasks'. Seems to be the flavor-du-jour.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. Was in the "task manager" frame of mind.
_includes/markdown/Tools.md
Outdated
|
||
[Gulp](http://gulpjs.com/) - Gulp is also a task runner build on Node that offers a similar suite of plugins and solutions to Grunt. The biggest difference is Gulp allows you direct access to the [stream](https://nodejs.org/api/stream.html) of information from your source files and allows you to modify this data directly. | ||
|
||
[Webpack](https://webpack.github.io/) - Webpack is a bundler - the next generation of JavaScript/CSS development tools. At 10up we are actively building new projects with this library to expand our internal knowledge and find the best use cases. Webpack allows us to combine all of good parts of the above mentioned tools into a single file/command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I understand what this means: "actively building new projects with this library to expand our internal knowledge and find the best use cases"
Expanding the Task Runner section to include Gulp/Browserify/Webpack.