Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


Boilerplate for developing Elm apps on Webpack

Subscribe to updates I use elm-webpack-starter

Statistics on elm-webpack-starter

Number of watchers on Github 840
Number of open issues 12
Average time to close an issue 6 days
Main language JavaScript
Average time to merge a PR 7 days
Open pull requests 9+
Closed pull requests 4+
Last commit almost 2 years ago
Repo Created over 3 years ago
Repo Last Updated over 1 year ago
Size 498 KB
Homepage http://elm-commun...
Organization / Authorelm-community
Page Updated
Do you use elm-webpack-starter? Leave a review!
View open issues (12)
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating elm-webpack-starter for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)



A simple Webpack setup for writing Elm apps:

  • Dev server with live reloading, HMR
  • Support for CSS/SCSS (with Autoprefixer), image assets
  • Bootstrap 3.3+ (Sass version)
  • Bundling and minification for deployment
  • Basic app scaffold, using Html.beginnerProgram
  • A snippet of example code to get you started!


Clone this repo into a new project folder, e.g. my-elm-project:

git clone my-elm-project
cd my-elm-project

Re-initialize the project folder as your own repo:

rm -rf .git         # on Windows: rmdir .git /s /q
git init
git add .
git commit -m 'first commit'

Install all dependencies using the handy reinstall script:

npm run reinstall

This does a clean (re)install of all npm and elm packages, plus a global elm install.

Serve locally:

npm start
  • Access app at http://localhost:8080/
  • Get coding! The entry point file is src/elm/Main.elm
  • Browser will refresh automatically on any file changes..

Build & bundle for prod:

npm run build
  • Files are saved into the /dist folder
  • To check it, open dist/index.html


Ver 0.8.6

  • Update Packages (-> Webpack 2)
  • fix paths in file-loader
  • clean up build script

Ver 0.8.5

  • Fix loading path of generated js file, per Issue 47

Ver 0.8.4

  • Fix hot reloading of components, per Issue 44

Ver 0.8.3

  • Update packages
  • Attempt to fix path issues when building for prod (temp)

Ver 0.8.2

  • Webpack config improvements (PR by Lesuk)

Ver 0.8.0

  • Update to Elm 0.18, use debug=true on webpack loader (PR by douglascorrea)
  • Add a script for one-step installs
  • Update to latest packages

Ver 0.7.1

Ver 0.7.0

  • Modify project structure, per Issue 26
  • Include Bootstrap JS, per Issue 28
  • More helpful install steps in README, per Issue 29
  • Update to latest packages

Ver 0.6.2

  • Use copy-webpack-plugin instead of cp to copy files (Windows compatible)

Ver 0.6.0

  • elm-hot-loader is back (no Elm code changes required!)
  • Switch to bootstrap-sass to demo CSS

Ver 0.5.0

  • Update to Elm 0.17.0 (and other latest modules)
  • Upgrade starter code per upgrade-docs
  • Remove elm-hot-loader (for now)

Ver 0.4.0

Ver 0.3.0

  • Use html-webpack-plugin to generate index.html
  • Apply hash filenames for bundled JS and CSS (prevents caching)
  • Image and favicon assets copied to dist/
elm-webpack-starter open issues Ask a question     (View All Issues)
  • over 2 years Include unit tests and fuzz tests in the starter
  • over 2 years Upgrade to Webpack 2
  • over 2 years Small confusion in readme with respect to `npm run build`
elm-webpack-starter open pull requests (View All Pulls)
  • Redoing setup into Elm architecture
  • Upgrade to Webpack 2
  • Replace `reinstall` script with a simpler `postinstall`
  • upgrade to webpack 2
  • Remove duplicates from webpack config
  • To also minimize the css file in dist folder.
  • Upgrade all packages
  • Set webpack publicPath to allow for nested url paths
  • add missing dependency
elm-webpack-starter list of languages used
Other projects in JavaScript