webpack build task

A build task for Visual Studio Team Services (VSTS) made with ♥ by

to bundle your assets, scripts, images and styles with webpack.

Content

• Installation
• Source Code
• What The Build Step Does
• Usage
  • Advanced Settings
  • Multiple Build Steps
• Summary of Task Settings
• Release Notes
• License

Installation

Installation can be done using Visual Studio MarketPlace.

Source Code

Source code can be found on GitHub.

What The Build Step Does

This build step is using the webpack's command line tool to compile a 'web' application into a bundle. The result, warnings and errors are reported onto the build summary section.

Usage

Add the task to your build configuration:

By default without any configuration the build task is trying to run the locally installed webpack.js from the root folder in the repository and trying to pick up the webpack.config.js.

Through the webpack cli arguments setting custom arguments can be passed to the webpack cli:

-p --display normal

Errors and Warnings can be treated differently:

• treat errors as (errors / warnings / info)
• treat warnings as (errors / warnings / info)

Warnings means the task will partially succeed, in case of errors the task will fail. If there are no errors and no warnings, then the task will succeed. You can treat the errors as warnings, so in case of errors, the task will just partially succeed. Or if you would like to ignore the warnings, those should be handled as info.

The webpack build errors and warnings are reported under the issues / build section on the summary page:

The webpack build result section is added onto the summary page to summarize the result:

Advanced Settings

• Working folder where webpack command is run. If you leave it blank it is the root of the repo.
• Location of the webpack cli. By default it is the locally installed webpack node module in the working folder, e.g. ./node_modules/webpack/bin/webpack.js.
• Location of the Stats.js. By default it is the locally installed webpack node module in the working folder, e.g. ./node_modules/webpack/lib/Stats.js.

Multiple Build Steps

Multiple webpack build steps are supported now. To distinguish the webpack build steps on the summary page and in the list of issues, set the display name properly for the steps:

If the webpack projects are not even in the root folder, then don't forget to modify it in the advanced settings like this:

The issues in case of multiple build steps:

The result sections in case of multiple build steps:

Summary of Task Settings

Release Notes

• 4.2.0 (13/08/2019)

  • Node.js arguments are supported.

• 4.1.6 (21/06/2019)

  • Security warnings are fixed

• 4.1.5 (18/06/2019)

  • New build/deployment badge on README page. (as build and deployment are on travis-ci.org)

• 4.0.4 (24/05/2018)

  • Dependencies are updated to fix security vulnerabilities (though it was just in one of the samples).

• 4.0.3 (29/03/2018)

  • The --display "none" flag is working properly with webpack 4.

• 4.0.2 (27/01/2018)

  • Documentation is updated.

• 4.0.1 (27/01/2018)

  • Errors and Warnings are reported correctly in the webpack like logs based on the --display none/errors-only/minimal/normal/detailed/verbose option.

• 4.0.0 (27/01/2018)

  • Using webpack-cli again instead of node.js API.

• 3.2.2 (03/10/2017)

  • Avoid webpack task summary section overflow with adding scrollbar.
  • Webpack task summary section uses same font as other sections.

• 3.2.1 (22/09/2017)

  • Replacing [] brackets to () parenthesis in the title of the result summary section.

• 3.2.0 (22/09/2017)

  • Support [] brackets in the display name of the task.

• 3.1.0 (21/09/2017)

  • Support for TypeScript webpack configuration is added.
  • The ts-node module location can be modified.
  • The ts-node module options file location can be supplied.

• 3.0.19 (03/07/2017)

  • As the build step is using webpack's node.js API the arguments setting is gone. Instead of that there's the webpack config file location where custom configuration files can be specified for the compilation.
  • The setting of webpack.js location is gone, instead of that use webpack module location if you don't want to use the locally installed webpack module.
  • The webpack build step summary section is using webpack node.js API to show the result information.
  • The webpack build step now is logging the summary section onto the log section as well.

• 2.1.3 (22/05/2017)

• 2.1.2 (22/05/2017)

• 2.1.0 (22/05/2017)

• 2.0.2 (16/05/2017)

• 1.1.1 (29/03/2017)

• 1.1.0 (21/01/2017)

License

MIT