middleman-webpack-demo is a starter Middleman 4.2 site whose JavaScript and stylesheets are built by webpack 2 instead of Middleman’s own asset pipeline. It’s a demo: the page is Middleman’s default “Middleman is Running” welcome page, and the JavaScript only imports the stylesheet and logs a message to the console. What it shows is the wiring between the two tools. It was made over two days in February 2017 and hasn’t changed since.
How it fits together
Middleman’s external_pipeline extension runs webpack next to the site. In development it starts webpack --watch, and in a build it runs webpack --bail -p. Either way, Middleman treats whatever webpack writes to .tmp/dist as part of the site’s source.
webpack starts from assets/javascripts/main.js. The JavaScript goes through Babel with the ES2015 and stage-0 presets, and the Sass it imports goes through sass-loader and css-loader into ExtractTextPlugin, which writes it out as its own CSS file. node-neat supplies the include paths for Bourbon and Neat, so the stylesheet can @import "bourbon" and @import "neat" without copying them into the project.

The layout links the two bundles with Middleman’s stylesheet_link_tag "main.bundle" and javascript_include_tag "main.bundle" helpers, and livereload is turned on. The second commit added an npm-build script and npm-webpack.config.js, which builds the same entry point into dist/javascript/roundup.js and dist/css/roundup.css, plus an .npmignore that leaves the Middleman files out of a package.
Running it today
Ruby isn’t needed for the webpack half. On Node 6, npm install still works, with the ^2.2.1 range resolving to webpack 2.7.0, and the build command from config.rb produces both bundles. Sass prints a deprecation warning from Bourbon along the way.

npm run npm-build doesn’t get that far. webpack 2 requires an absolute output path and npm-webpack.config.js gives ./dist, so it stops at config validation, with webpack 2.2.1 and with 2.7.0. The Middleman side wasn’t run for this page.
The creation date shown here is the GitHub repository’s UTC creation date. The terminal capture comes from running the repository’s webpack build locally on Node 6.17.1, and the code cards show the repository’s source files.