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

Utilize Vue-CLI, and latest packages #114

Open
4 tasks
MarkPieszak opened this issue Nov 19, 2018 · 3 comments
Open
4 tasks

Utilize Vue-CLI, and latest packages #114

MarkPieszak opened this issue Nov 19, 2018 · 3 comments

Comments

@MarkPieszak
Copy link
Member

MarkPieszak commented Nov 19, 2018

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

@Nordes
Copy link
Contributor

Nordes commented Nov 19, 2018

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).

@ow-en
Copy link

ow-en commented Dec 3, 2018

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,

@super2ni
Copy link

super2ni commented Jan 3, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants