Skip to content

Releases: salesforce/lwc-webpack-plugin

v3.1.0

19 Jun 20:24
1084063
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.0.5...v3.1.0

v3.0.5

13 Nov 21:16
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.0.4...v3.0.5

v3.0.4

13 Nov 21:11
3d5bf2f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.0.3...v3.0.4

v3.0.3

10 Jan 18:58
eac70b7
Compare
Choose a tag to compare

What's Changed

  • fix: add a warning when imported non-implicit CSS file is missing by @rui-rayqiu in #20

New Contributors

Full Changelog: v3.0.2...v3.0.3

v3.0.2

01 Sep 15:38
81a3f33
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.0.1...v3.0.2

v3.0.1

22 Aug 17:49
3e1b864
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.0.0...v3.0.1

v3.0.0

29 Mar 17:28
f56ed8c
Compare
Choose a tag to compare

Breaking changes

lwc and @lwc/module-resolver are now peer dependencies

Rather than bundling its own version of lwc (and other @lwc/* packages), lwc-webpack-plugin now requires lwc and @lwc/module-resolver to be installed as peer dependencies.

Run:

npm install --save-dev lwc@^2 @lwc/module-resolver@^2

This allows you to upgrade lwc and @lwc/module-resolver at your own pace, rather than waiting for lwc-webpack-plugin to update its own bundled versions. Note that lwc and @lwc/module-resolver should have the same version.

TypeScript support is no longer built-in

Rather than handling TypeScript automatically, lwc-webpack-plugin now requires you to bring your own TypeScript toolchain. There are instructions in the README for how to accomplish this.