1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.