Discussion for "Retiring the Microsoft.AspNetCore.SpaTemplates package"

[SteveSandersonMS]

aspnet/Announcements#289

[RehanSaeed]

Totally get that you need to place limited effort where the crowd is going. Aurelia has decent templates they provide themselves. Vue seems to be getting more popular, what's criteria would it have to meet before it can be given first class support.

[mika76]

I'd also like to know what the criteria is for choosing which frameworks are "officially" supported.

Vue has definitely risen in interest in the last couple of years (as seen with this google trends comparison and I think should still be considered.

Blue-Vue, Red-React (Angular is too popular and including it makes the graph hard to compare)

[dasMulli]

Just to be sure: this is limited to the templates and not the underlying JavaScriptServices and/or SpaServices (prerendering)?

[RehanSaeed]

This is a more fair comparison of ReactJS (Note that there is no dot) and Vue.js. React is one third more popular than Vue at the moment.

[SteveSandersonMS]

Just to be sure: this is limited to the templates and not the underlying JavaScriptServices and/or SpaServices (prerendering)?

You are correct. The underlying JavaScriptServices/SpaServices packages (including prerendering helpers) are a fully supported, shipping part of ASP.NET Core. We have no plans to stop working on them. They are required for our Angular/React support, which as mentioned in the announcement, is something we're continuing to invest in. It's only the Aurelia/Knockout/Vue templates we're no longer developing and asking for interested community members to take over.

[mika76]

@RehanSaeed Interestingly the graph changes again if you compare both without dots (vuejs vs reactjs) and you can clearly see that vue has become a force in the javascript world.

It seems to me the only officially supported frameworks are the ones backed by large companies. I guess it's understandable but sad.

[awulkan]

@RehanSaeed If you compare the names with a dot in both, or without a dot in both, Vue wins.
You can't compare one with a dot and the other without it, that's misleading.

https://trends.google.com/trends/explore?date=today%205-y&q=vuejs,reactjs,vue.js,react.js

[Alexander-Taran]

oranges and apples
https://trends.google.com/trends/explore?date=today%205-y&q=vuejs,reactjs,electron
(-:

[mcquiggd]

Slightly surprised at the dropping of official support for Vue, with the industry adoption rapidly increasing.

But, It's not a huge loss.

The Visual Studio and Visual Studio Code teams have made strong efforts to support Vue; the latest release of Code offers syntax highlighting, support for single file components, snippets, debugging recipes posted by a Program Manager of the Code team. Visual Studio offers similar support thanks to Mads Christensen.

Personally I would recommend people look to Nuxt for SSR, PWA, and static site generation, and maybe use WebAPÌ or go 'serverless'. The Microsoft developer tooling for those combinations is very good; it`s a more flexible approach combining the best of current technologies without munging them together, and solves the core problems that most people wanted to address with Vue and NodeServices / JavaScriptServices.

P.S I always take Google trends with a pinch of salt. The only thing it highlights is the importance of naming your product to be something that is not easily confused with other common words (or the reverse, if you want to appear 'popular')

[lancescole]

I really liked the Aurelia version. I installed it and it just worked. It's so easy to use. I hope someone will take on the support for Aurelia.

This decision does make sense. Vue and Aurelia were already way ahead in terms of their CLI implementations. Vue has Nuxt and a whole host of integrations with more suitable Node implementations. Express, Hapi, Koa, Feathers with websocket support templates already exist for Vue/ Nuxt. It will always move faster.

This project is Angular first, React second. Its target is to keep .Net being used by slow moving large companies and stop them looking at other technologies that is all.

[pkellner]

For React, is the official decision to only support create-react-app and not redux or server side rendering in React?

Will The new react CRA template be released at the same time as 2.1 (Hunter's roadmap said summer time frame if I'm not mistaken)

Want to confirm that the old React templates will not be supported or maintained in any way by Microsoft.

[tpetrina]

CRA doesn't have SSR so the new template(s) won't have it either. Same for TypeScript support.