v5.0.0

Breaking changes

• html-webpack-plugin@3 is no longer supported (#27)

Bug fixes

• Remove duplicated publicPath by @karoldeland in #27

New Contributors

• @karoldeland made their first contribution in #27

Full Changelog: v4.0.0...v5.0.0

v4.0.0

What's Changed

• Upgrade all dependencies, add support for multiple import map urls by @joeldenning in #25

Full Changelog: v3.0.0...v4.0.0

v3.0.0

Features

• Add startOptions option. Change urlRerouteOnly default to true. (#17)

To learn more about urlRerouteOnly, see https://single-spa.js.org/docs/api#start

new StandaloneSingleSpaPlugin({
  startOptions: {
    // in standalone-single-spa-webpack-plugin@2, the default value was false. In v3, the default value is true.
    urlRerouteOnly: false
  }
})

This change was made to make it easier for Vue 3 applications to work in standalone mode. See single-spa/single-spa-vue#85

v2.1.0

Features

• Support for passing customProps as an option (#16)

v2.0.2

Fixes

• Give better error messages when standalone plugin is applied twice to the webpack config (#14)

v2.0.1

Fixes

• Add polyfills for IE11 support (#12)

v2.0.0

Breaking changes

If you use standalone-single-spa-webpack-plugin for development purposes only, it is 100% safe to upgrade. If you use it in production, you'll want to set some new configuration options when you upgrade.

• import-map-overrides UI will now show up in the browser page, by default. This can be turned off with the importMapOverrides or importMapOverridesLocalStorageKey options.

Features

• Added import-map-overrides to standalone page, including importMapOverrides and importMapOverridesLocalStorageKey options. (#11)

v1.2.2

Fixes

• Include type declearations in published tarball (#9)

v1.2.1

Fixes

• Adding script for regenerator runtime. (#7) 8c4ae6d

v1.2.0...v1.2.1

v1.2.0

Features

• Support for html-webpack-plugin@3. Resolves #3. (#6) 516f4cc

v1.1.0...v1.2.0