-
Notifications
You must be signed in to change notification settings - Fork 517
Conversation
…e docs recommend, and apparently the only way it does encapsulation)
Glad to of helped! I was originally going to go all TypeScript as well, but we stuck with ES6 just because it seems that the Vue community usually uses ES5 (sometimes 6), and I can't recommend anyone use ES5 (that's just crazy) :) At least everyone will have both options now! I'll make sure to label mine ES6. Also, I need to finally take the time to push my repos to |
Merged. |
Do you want to add it to the wiki? https://github.com/aspnet/JavaScriptServices/wiki
There are a few blog posts going around on this subject, e.g., http://dotnetthoughts.net/create-a-dot-net-new-project-template-in-dot-net-core/ |
I don't have write access to add anything in there :( @SteveSandersonMS |
Sorry - I thought it was world-writable. Also I don't have permission to add permissions :( So I've added the link myself. |
Yeah for some reason doesn't show you as a Member of ASPNET even though I know you are! Strange 😆 Going to link to this one for the TypeScript version. Thanks again Steve, hope all is well over in the UK. |
The membership was set to 'private' for some reason. I have now changed it to 'public'. |
There it is! :) |
As per all the requests in #524, here's a PR that adds a Vue.js template. This takes inspiration in various ways from @MarkPieszak's aspnetcore-Vue-starter, but also has some differences:
I'm putting this here as a PR in case anyone who is particularly familiar with Vue has comments on the approach or can suggest improvements.
Why there's no server-side prerendering
I did set it up with server-side prerendering. If you want that, look at commit 2067ea2. But then when trying to add a reference to
node-fetch
(so that API calls can occur on the server too), I realised there were some severe limitations, so I removed server-side prerendering support. See #754 for details of these issues - when people ask for server-side Vue rendering, we can point them to that issue. Hopefully, someone more involved in the Vue project might be able to suggest solutions or to fix the underlying limitations in Vue's approach to SSR.