aspnetcore-Vue-starter
aspnetcore-Vue-starter copied to clipboard
Utilize Vue-CLI, and latest packages
This will help us stay up-to-date with Vue, and let people not have to configure their own Webpack setup.
- [ ] Update to use Vue-CLI
- [ ] Upgrade any packages needed (dotnet or otherwise)
- [ ] Move current webpack setup to a webpack branch
- [ ] Release to dotnet template
cc/ @owensource
Hi @markpieszak, in my repository I recreated from scratch a vuejs template using webpack and latest version of everything. If you want, you can look at how I have put webpack 4 and latest version of babel (etc). However the rest of the templates are different (picnicss, i18n dynamic loading and etc).
Hi Mark - sorry for the late response on this. The primary reason I haven't yet is due to a timeout error that is plaguing the angular-cli/vue-cli middleware packages.
Essentially, when you start the project through IIS, the vue-cli middleware package runs vue-cli's built-in build process. This build process forwards the built development environment/port to IIS's kestrel reverse proxy, where it is picked up and served on Visual Studio/IIS's native port. The problem seems to be that vue-cli's build process doesn't complete before IIS's listener time outs, on roughly 2/3 attempts.
The end result is that you often need to run IIS 4, 5, 7, 11 times before the vue-cli build and IIS's listener sync up correctly. When it works, it works great- with HMR fully functional. Unfortunately, the timeout error happens more often than not, resulting in a tedious, annoying development process at times. This issue isn't limited to vue-cli, however. As mentioned, angular-cli suffers from this problem as well. To my knowledge, MS hasn't posted a definitive solution yet.
The good news, though, is that I think I've found a workaround for this issue. It's a bit hacky, but it dramatically improves the end result. I'm still playing around with it, however. I'll put together a PR this week for you to look at, and we can go from there-
Thanks,
Hello @owensource ,
I'm undergoing the "timeout" issue. You said you would put a PR correcting it. Did you have the chance and time to do it?
Thank you, Denis