A Visual Studio extension
Switch branches/tags
Nothing to show
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Added .github folder and optimized images Feb 24, 2016
Backup Added support for VS 16.0 Sep 12, 2018
src Merge branch 'master' of https://github.com/madskristensen/WebPackTas… Sep 12, 2018
.editorconfig Initial commit Dec 10, 2015
.gitattributes Initial commit Dec 10, 2015
.gitignore Initial commit Dec 10, 2015
LICENSE Mention support for VS2017 (#46) Oct 17, 2017
README.md Mention support for VS2017 (#46) Oct 17, 2017
WebPackTaskRunner.sln Added support for VS 16.0 Sep 12, 2018
appveyor.yml Update appveyor.yml May 18, 2017


WebPack Task Runner extension

Adds support for the WebPack build tool in Visual Studio 2015 and Visual Studio 2017's Task Runner Explorer.

Build status

Download the extension at the VS Gallery or get the nightly build

New to WebPack?

You may want to check out the article How to integrate WebPack into Visual Studio 2015 by Ilya Pirozhenko, which applies equally to VS2017.

Install WebPack

In order to use this extension, you must have WebPack installed globally or locally in your project.

Use npm to install it globally by typing the following in a command line:

npm install webpack -g

To use the server functionality you also need to install webpack-dev-server like so:

npm install webpack-dev-server -g

If you wish to use babel to run WebPack, you must first install it locally in your project:

npm install babel-core --save-dev

Config files

The WebPack Task Runner automatically triggers when it finds WebPack configuration files. The following file names are supported:

  • webpack.config.js
  • webpack.config.ts
  • webpack.config.coffee
  • webpack.config.babel.js

Important! The Task Runner Explorer requires the config files to be located at the root of the project or solution - not in a project sub folder.

Any config file will have a WebPack logo watermark at the bottom right corner of the editor window.


You can toggle the visibility of the watermark by clicking on it.

Dev server

This extension supports webpack-dev-server and can invoke it through the Task Runner Explorer.

Make sure to setup the details in the webpack.config.js file like so:

devServer: {
    contentBase: ".",
    host: "localhost",
    port: 9000

Task Runner Explorer

Open Task Runner Explorer by right-clicking the WebPack configuration file and selecting Task Runner Explorer from the context menu:

Open Task Runner Explorer

The following tasks are supported:

  • Run
    • Run - Development: webpack -d --color
    • Run - Production: webpack -p --color
  • Profile
    • Profile - Development: webpack -d --profile --json > stats.json
    • Profile - Production: webpack -p --profile --json > stats.json
  • Serve
    • Hot: webpack-dev-server --hot
    • Cold: webpack-dev-server
  • Watch
    • Watch - Development: webpack -d --watch --color
    • Watch - Production: webpack -p --watch --color

Task List

Each task can be executed by double-clicking the task.

Console output


WebPack CLI switches are available on the left-hand side toolbar. The switches are:

  1. --display-modules
  2. --display-reasons
  3. --display-chunks
  4. --display-error-details
  5. --bail
  6. --inline


Each switch enabled will be added to the arguments when invoking the WebPack CLI.

The --progress switch is not supported in this extension due to Task Runner Explorer's inability to handle it.

All switches are toggle buttons that can be left on or off for as long as needed.

Development / Production

When executing a Production task, the extension will automatically set NODE_ENV to production. For Development tasks, development will be the value.

SET NODE_ENV=production&& webpack...


Task bindings make it possible to associate individual tasks with Visual Studio events such as Project Open etc.


Item Template

You can easily add a new webpack.config.js file to your project from the Add New Item dialog.

Just search for "webpack".

Item template


Apache 2.0