Not an issue / but a generic question

Please understand I completely like this generator. I think this will be great starting point.

As we progress to develop projects using angular and nodejs. We are looking for a generator that will continue to support Angular 1. As we see in fullstack it is currently moving to Angular 2 with version 5 that means not now but in near future Angular 1 would work but may not be area of focus.

I would want to understand if anyone is already aware of this - when is the tipping point. It maybe when majority of the contributors on this project feel that they are ready to move to Angular 2, but the start of the framework and 5.0.0 branch indicates that it is not too far.

Is my question relevant to this forum?

[stherrienaspnet]

Glad you're asking this question, because I'm in the same situation

[Awk34]

Once 5.0.0 is released, I will try to support 4.x.x as much as I can, but it always helps to have community support too 😉

Sorry if I may ask what is the timeline we should be looking for 5.0 to become mainstream and 4.x to kind of retire?

[Awk34]

@lazyspark I'm not sure. There's a lot I'd like to get done before 5.0.0 is released. As for 4.0.0, it will probably go into 'maintenance' mode. Everyone will still be free to submit PR's for 4.x.x, but I personally probably won't do any feature work for it.

[atodicebear]

Ive checked the Changelog but could not Clarify what are the Main Changes between 3.x 4.x 5.x ?
Iam using 3.x and see much changes but they effect mostly 4.x and soon 5.x.
So what are the Changes from 3 to 4? ( Only Webpack? I thought it was for Angular2.x?)
4 to 5?

[Awk34]

@atodicebear I believe the changelog spells it out pretty well: https://github.com/angular-fullstack/generator-angular-fullstack/blob/master/CHANGELOG.md#400-2016-08-08

5.0.0 is still in flux. Mainly moving to Angular 2

Is this an opportunity to separate the backend generator from the frontend generator? This way both can evolve separately?

[Awk34]

@lazyspark that's never been the intent of this generator, and probably will be the opposite of the direction we move towards. It is a full-stack generator. I aim to achieve even tighter coupling between the front-end and back-end.

@Awk34 as things move in Angular 2 direction will it would impact how backend is structured right?

For example you may have more of TypeScript given that Angular 2 is TypeScript first. There will be services around AOT and others

[Awk34]

@lazyspark The back-end structure shouldn't change for the most part. The only big change I see is splitting the Mongo schema files out so that they can be used for validation on both the front-end and back-end.

I would also like to have Angular AOT & Universal implemented before 5.0.0 is released.

[Jscott388]

Where is the repo for 5.0.0 alpha?

[stherrienaspnet]

The branch name is canary :)

…

On Thu, Jul 20, 2017 at 3:21 PM, Joshua Scott ***@***.***> wrote: Where is the repo for 5.0.0 alpha? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2406 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF19cfpuP6eJXy3dMeQ9jR2COWjZgYC_ks5sP6i6gaJpZM4LN9ID> .

--