Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET Core run fails with missing module exception #1072

jmoerdyk opened this Issue Mar 20, 2019 · 0 comments


None yet
1 participant
Copy link

jmoerdyk commented Mar 20, 2019

I'm submitting a bug report

  • Library Version:

Please tell us about your environment:

  • Operating System:
    Windows 10

  • Node Version:

  • Yarn Version:

  • Browser:

  • Language:

  • Loader/bundler:

Current behavior:
For the .Net Core platform, the clean-webpack-plugin is now missing, so running the project
with the dotnet run command produces an exception on startup.

Create new project with the following options:
√ Would you like to use the default setup or customize your choices? · Custom App
√ Which bundler would you like to use? · Webpack
√ Which HTTP Protocol do you wish the outputted Webpack bundle to be optimised for? · HTTP/1.1
√ What platform are you targeting? · .NET Core
√ What transpiler would you like to use? · TypeScript
√ How would you like to setup your HTML template? · None
√ What css processor would you like to use? · None
√ Do you want to add PostCSS processing · None
√ Which unit test runner would you like to use? · None
√ Would you like to configure integration testing? · None
√ What is your default code editor? · Visual Studio Code
√ Which features do you want scaffolded into your project? · Navigation App

Run dotnet run

Fails with exception:

Application startup exception: System.AggregateException: One or more errors occurred. (Cannot find module 'clean-webpack-plugin'
Error: Cannot find module 'clean-webpack-plugin'

If I add the "clean-webpack-plugin": "^0.1.19" back to the devDependencies as it was in beta13, the project runs normally.

  • What is the expected behavior?

Project runs without error

  • What is the motivation / use case for changing the behavior?
    This is a bug, a new project should run out of the box with no modification.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.