Overview

Yeoman

Stacks1.7K

Followers1.3K

Votes396

GitHub Stars10.1K

Forks730

Webpack

Stacks41.6K

Followers28.1K

Votes752

GitHub Stars65.7K

Forks9.2K

Webpack vs Yeoman: What are the differences?

File Bundling and Code Compilation: Webpack focuses on bundling various assets, such as JavaScript files, CSS files, images, etc., into a more optimized and manageable format, whereas Yeoman is more focused on providing generators to scaffold out new projects and automate repetitive tasks.
Loaders and Plugins: Webpack makes use of loaders and plugins to process different types of files, apply transformations, and optimize the output bundle, while Yeoman provides a generator ecosystem to scaffold out projects with specific configurations and dependencies.
Configuration Complexity: Webpack requires a more detailed configuration setup to define the entry point, output path, loaders, plugins, and other settings, making it suitable for complex projects with specific requirements, whereas Yeoman simplifies project initialization by using predefined generators that include common project setups.
Built-in Development Server: Webpack comes with a built-in development server to serve the bundled assets locally and hot reload changes in real-time, improving the development workflow, whereas Yeoman focuses on project scaffolding and does not provide a development server out of the box.
Module Bundling: Webpack treats every file in the dependency graph as a module, allowing for code splitting and dynamic imports, while Yeoman's focus is on project setup and generating boilerplate code rather than module bundling.
Ecosystem Integration: Webpack is commonly used as part of a wider JavaScript ecosystem along with tools like Babel, ESLint, and Node.js, whereas Yeoman serves as a standalone tool for project scaffolding and automation, with less integration with other tools.

In Summary, Webpack and Yeoman differ in their focus on file bundling and code compilation, use of loaders and plugins, configuration complexity, built-in development server, module bundling approach, and ecosystem integration.

Advice on Yeoman, Webpack

Aleksandr

Contract Software Engineer - Microsoft at Microsoft-365

Dec 23, 2019

Decided

Why migrated?

I could define the next points why we have to migrate:

Decrease build time of our application. (It was the main cause).
Also jspm install takes much more time than npm install.
Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.

301k views301k

Comments

Abigail

Dec 10, 2019

Decided

We mostly use rollup to publish package onto NPM. For most all other use cases, we use the Meteor build tool (probably 99% of the time) for publishing packages. If you're using Node on FHIR you probably won't need to know rollup, unless you are somehow working on helping us publish front end user interface components using FHIR. That being said, we have been migrating away from Atmosphere package manager towards NPM. As we continue to migrate away, we may publish other NPM packages using rollup.

224k views224k

Comments

Detailed Comparison

Yeoman	Webpack
Yeoman is a robust and opinionated set of tools, libraries, and a workflow that can help developers quickly build beautiful, compelling web apps. It is comprised of yo - a scaffolding tool using our generator system, grunt - a task runner for your build process and bower for dependency management.	A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Lightning-fast scaffolding — Easily scaffold new projects with customizable templates (e.g HTML5 Boilerplate, Bootstrap), RequireJS and more.;Great build process — Not only do you get minification and concatenation; I also optimize all your image files, HTML, compile your CoffeeScript and Compass files, if you're using AMD, I will pass those modules through r.js so you don't have to.;Automatically compile CoffeeScript & Compass — Our LiveReload watch process automatically compiles source files and refreshes your browser whenever a change is made so you don't have to.;Automatically lint your scripts — All your scripts are automatically run against JSHint to ensure they're following language best-practices.;Built-in preview server — No more having to fire up your own HTTP Server. My built-in one can be fired with just one command.;Awesome Image Optimization — I optimize all your images using OptiPNG and JPEGTran so your users can spend less time downloading assets and more time using your app.;Killer package management — Need a dependency? It's just a keystroke away. I allow you to easily search for new packages via the command-line (e.g. `bower search jquery`), install them and keep them updated without needing to open your browser.;PhantomJS Unit Testing — Easily run your unit tests in headless WebKit via PhantomJS. When you create a new application, I also include some test scaffolding for your app.	Bundles ES Modules, CommonJS, and AMD modules (even combined); Can create a single bundle or multiple chunks that are asynchronously loaded at runtime (to reduce initial loading time); Dependencies are resolved during compilation, reducing the runtime size; Loaders can preprocess files while compiling, e.g. TypeScript to JavaScript, Handlebars strings to compiled functions, images to Base64, etc; Highly modular plugin system to do whatever else your application requires
Statistics
GitHub Stars 10.1K	GitHub Stars 65.7K
GitHub Forks 730	GitHub Forks 9.2K
Stacks 1.7K	Stacks 41.6K
Followers 1.3K	Followers 28.1K
Votes 396	Votes 752
Pros & Cons
Pros 121 Lightning-fast scaffolding 83 Automation 78 Great build process 57 Open source 49 Yo Cons 1 Even harder to debug than Javascript	Pros 309 Most powerful bundler 182 Built-in dev server with livereload 142 Can handle all types of assets 87 Easy configuration 22 Laravel-mix Cons 15 Hard to configure 5 No clear direction 2 SystemJS integration is quite lackluster 2 Spaghetti-Code out of the box 2 Fire and Forget mentality of Core-Developers
Integrations
Bower Grunt	JavaScript

What are some alternatives to Yeoman, Webpack?

gulp

Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes.

Grunt

The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it, a task runner can do most of that mundane work for you—and your team—with basically zero effort.

Brunch

Brunch is an assembler for HTML5 applications. It's agnostic to frameworks, libraries, programming, stylesheet & templating languages and backend technology.

Parcel

Parcel is a web application bundler, differentiated by its developer experience. It offers blazing fast performance utilizing multicore processing, and requires zero configuration.

rollup

It is a module bundler for JavaScript which compiles small pieces of code into something larger and more complex, such as a library or application. It uses the new standardized format for code modules included in the ES6 revision of JavaScript, instead of previous idiosyncratic solutions such as CommonJS and AMD.

Backpack

Backpack is minimalistic build system for Node.js. Inspired by Facebook's create-react-app, Zeit's Next.js, and Remy's Nodemon, Backpack lets you create modern Node.js apps and services with zero configuration. Backpack handles all the file-watching, live-reloading, transpiling, and bundling, so you don't have to.

Vite

It is an opinionated web dev build tool that serves your code via native ES Module imports during dev and bundles it with Rollup for production.

Pingy CLI

Gulp and Grunt and other heavyweight build tools are great for complicated build workflows. Sometimes you want something simpler that doesn't take lots of configuration to get up and running. That's Pingy CLI.

System.js

It is a Universal Module Loader for JavaScript. If you've used RequireJs or a CommonJs bundler in the past, you have probably created modules.Configurable module loader enabling dynamic ES module workflows in browsers and NodeJS.