TypeError: CleanWebpackPlugin is not a constructor

[ghost]

Issue description or question

In the docs is wrong the way get the plugin variable, it's distructuring the module unnecessarily:

const { CleanWebpackPlugin } = require('clean-webpack-plugin');

Doing that way, triggers this error:

TypeError: CleanWebpackPlugin is not a constructor

The right is:

const CleanWebpackPlugin = require('clean-webpack-plugin');

Webpack Config

const path = require('path');

const CleanWebpackPlugin = require('clean-webpack-plugin');

module.exports = {
    mode: 'development',
    entry: {
        newtab: './src/newtab.js'
    },
    output: {
        filename: '[name].js',
        path: path.resolve(__dirname, 'dist')
    },
    plugins: [
        new CleanWebpackPlugin(),
    ],
};

Environment

Run: npx envinfo --system --binaries --npmPackages clean-webpack-plugin,webpack

  System:
    OS: Windows 10
    CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
    Memory: 3.67 GB / 7.88 GB
  Binaries:
    Node: 10.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.13.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

Please, test the things before put in the docs and test the installation of module before publish it to Github because it can confuse the users, thanks!

[gustawdaniel]

I have the same error.

To fix use

const CleanWebpackPlugin = require('clean-webpack-plugin');

instead of

const { CleanWebpackPlugin } = require('clean-webpack-plugin');

so docs is broken.

I see that this was changed 6 days ago in d0e3408 and described in #114

Last release v2.0.2 is from 22 days ago · 20 commits to master since this release

So everything clear. In official Readme is described how to install next (not released) version, but it is breaking change so in my opinion it should not be merged into master but in branch dev or versioned branch.

Anyway: if you have this error now use

const CleanWebpackPlugin = require('clean-webpack-plugin');

for last released version v2.0.2

[gustawdaniel]

Other solution is change default displayed branch from master to lts or last stable release or something like this because of many end users see README.md on main page as source of knowledge about last released version.

[bigbossx]

@gustawdaniel it's right
const CleanWebpackPlugin = require('clean-webpack-plugin');

[chrisblossom]

It is normal for a github project's readme to be out of date with what is published on npm. Either use github tags or view the readme from the npm page.

[johnagan]

released fixed in v3.0.0