webpack-cleanup-plugin | Plugin for webpack to cleanup the output path | Plugin library

If you want to run the cleanup plugin but don't want webpack to bundle your files then that's not possible because primary goal of webpack is to bundle your dependencies and taks like cleanup are add-ons

There is probably a better way to do this thing but to answer your question

without having to configure the entry or output parameters?

yes this is possible with Webpack 4 if you don't specify entry or output parameter it will use the default values which is src/index.js for entry and dist for output.folder

Webpack will throw a error if entry file is not found so if you dont specify entry then src/index.js must be present in your project

so lets say your folder structure is as following

You have the package referred to in both sections of your dependencies; you should totally not do this because it means that your production install will have a different version to your development install.

If you do npm install you will get all dependencies & devDependencies installed; however if you do npm install --production you only get dependencies installed.

You should remove things you don't need for your app to run from dependencies and place them in devDependencies. Things in dependencies should be seen as requirements to run the application (after any code transformation has occurred).

There is zero case where a dependency should be in both.

I found solution - disabled node modules cache on Heroku:

It turns out that currently (5/2017) the built in webpack.optimize.UglifyJsPlugin does not support ES6. When Babel transpiles await/async it turns them into generators, which causes UglifyJS to throw an error.

There are several alternatives to UglifyJS listed in this article, but I'm hoping that the Webpack guys will update the plugin, and I'd be able to leave my code intact.

TL;DR: My code is OK; UglifyJS does not support ES6; Will support in the future, or will be replaced by alternative.

If your test files are in a different directory, you might want to consider adding exclude property within the modules rules for js files.

Refer the following document: https://webpack.js.org/configuration/module/?_sm_au_=iVVKrMW7ZsbHQPbq#rule-exclude

or the following example: https://webpack.js.org/configuration/?_sm_au_=iVVKrMW7ZsbHQPbq#options

Another solution would be to use the IgnorePlugin. Docs for IgnorePlugin here: https://webpack.js.org/plugins/ignore-plugin/?_sm_au_=iVVKrMW7ZsbHQPbq

So in case anyone else runs into this problem. It appears it was a package version issue. Im assuming that the package versions specifically included in the boilerplate i used didn't play well with firebase.

I updated typescript, react-hot-loader, and most likely the issue webpack from version 3.0.4 to 4.12.1 and things seem to be working ok now. Also with the updates I now import firebase like so:

So I have refactored my code and realised that the problem was really in including circular dependency. I had to keep my code clean and simple and inject DI only where is really needed and use best practices like inheritance and global injection

Same issue here, wasn't able to update to typescript 2.2.1, last working version for me is 2.0.10.

Original source code contain babel source code, so it should be precompiled before installation.

You may remove lib from .gitignore, compile with npm run build and commit compiled code in lib folder. Then it can be installed from github