Chris Blossom

You most likely are using the [`allowJs` and/or `checkJs` option](https://www.typescriptlang.org/docs/handbook/compiler-options.html), which you'd still need `@types/webpack`. That or set webpack to ignore your webpack config

Moved `@types/webpack` to dependencies in https://github.com/johnagan/clean-webpack-plugin/pull/136.

@Sebazzz please provide a repository showing this and/or link showing why/when this could happen.

This is definitely causing a problem, but am unsure what to do to fix it. [@types/webpack-env](https://www.npmjs.com/package/@types/webpack-env) fixes some of the problems. I think we probably need to remove the `@types/webpack`...

> If someone is experimenting an error because it's now installed automatically, they will keep facing it if you remove and then they install it manually (on a project that...

Thanks @rdsedmundo for tracking down the jquery issue! This still leaves us with the `@types/webpack-env` issue. I think adding a note to the readme should be enough. What does everyone...

@pshurygin Have you installed `@types/webpack-env`? If so, what are the errors afterwards?

I get the error `Could not find a declaration file for module 'webpack'.` without `@types/webpack`.

It looks like `webpack@next` has some breaking changes that need to be addressed. I'll try and look into it as soon as I have some extra time.

Both `package-lock.json` and `yarn.lock` should be used for applications (but only one). In my opinion, libraries should not use lock files because the end user can (and will) end up...