Changes in version 2.0.0? #405

Closed
opened 2025-08-09 17:16:09 +00:00 by fergalmoran · 0 comments
Owner

Originally created by @jsfeldman on 9/22/2017

I'm trying to upgrade all my .NET packages to 2.0.0, however, I'm having difficulty running my development webpack configuration using SpaServices/WebpackDevMiddlewareOptions with the 2.0.0 package. I've updated aspnet-webpack to 2.0.1. Are there any other changes I need to make in order to upgrade to 2.0.0? I'm just using the vue-cli webpack template configuration, so I don't think I'm doing anything too unique.

It seems to complain about webpackJsonp being undefined, but since my development configuration doesn't even use the CommonsChunkPlugin (as mentioned here) and the code also appears minified even though it's not configured to minify in development I believe my code might be building wrong. I thought it might be building using production's configuration, but I commented out that configuration file and it is still building the same way.

I tried looking into possible causes from other projects but I believe I narrowed it down to upgrading the package (it seems to run fine by just calling webpack-dev-server directly from the command line).

Has anyone else experienced this issue? Let me know if there is any other information I could give you that would be helpful or if I should ask anywhere else.

*Originally created by @jsfeldman on 9/22/2017* I'm trying to upgrade all my .NET packages to 2.0.0, however, I'm having difficulty running my development webpack configuration using SpaServices/WebpackDevMiddlewareOptions with the 2.0.0 package. I've updated aspnet-webpack to 2.0.1. Are there any other changes I need to make in order to upgrade to 2.0.0? I'm just using the vue-cli webpack template [configuration](https://github.com/vuejs-templates/webpack/tree/develop/template/build), so I don't think I'm doing anything too unique. It seems to complain about webpackJsonp being undefined, but since my development configuration doesn't even use the CommonsChunkPlugin (as mentioned [here](https://github.com/webpack/webpack/issues/368)) and the code also appears minified even though it's not configured to minify in development I believe my code might be building wrong. I thought it might be building using production's configuration, but I commented out that configuration file and it is still building the same way. I tried looking into possible causes from other projects but I believe I narrowed it down to upgrading the package (it seems to run fine by just calling webpack-dev-server directly from the command line). Has anyone else experienced this issue? Let me know if there is any other information I could give you that would be helpful or if I should ask anywhere else.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/JavaScriptServices#405
No description provided.