Closed void32 closed 3 years ago
We had the same issue. We were using an old version of WebPack to transpile.. after the plugin automatically updated, the only alternative is to update WebPack to a version that accepts mode as a parameter. We to looked for the old version of the VSIX, feeling that updating WebPack will become a PITA (which it has due to other JS packages version compat matching). We are going to forgo the pain of the upgrade, but mentioning it here as it will likely cause a lot of people a lot of pain.
We had the same issue, I still haven't solved it. what should i do
I've added a task called "Default" for both runs and profile that doesn't pass the --mode
argument. Please try out the latest CI build and let me know if this fixe.s it for you
Thanks @madskristensen !! This new build is working great for my ancient project.
@mroberts-btg Thanks for testing. I'll upload it to the Marketplace then
@madskristensen It's not working for my project... Is there any way to downgrade webpack task runner?
@HenryKwak there is not a way to downgrade. The marketplace don't keep old versions around, unfortunately. What error do you get now that --mode
is no longer added?
It's not working after installing latest version , "--mode" error is gone, but different errors
See here how webpack is called on the command line behind the scenes and tell me what it should do instead
Thanks, I've solved it another way.
Hi @madskristensen Thanks, I can confirm that the new "Run - Default" task works, however it would be nice with a watcher as well, to have it executed automatically. Is that possible?
Visual Studio automatically upgraded from WebPack Task Runner v1.5.94 to v1.5.101. This breaks our current dev environment as we are using an older version of webpack that does not support the mode argument:
Is there a place where we can download the vsix file for older releases of WebPack Task Runner?