Server rendered Angular websites in literal minutes... 

Oh this raises an interesting point, Angular on the backend is basically Nest... yeah 🤔

Man I tried this with v16 and Nest JS just seemed to be a pain because they've rejected providing ES modules so I ended up in module hell and my "fun" side project turned to misery.

@@toxaq I wouldn't think Angular and Nest should try to share anything or even be in the same repo. More so the thought is, Angular SSR in a sense should be (replace?) Nest

@@ianokay The express portion of the nest integration needs to use angular universal for the SSR. I wish the Angular team would just pick up Nest and then we'd have integrated server and client end to end dev platform. Would be awesome. I enjoyed working in Nest.

@@ianokay Just think about T3 Stack and it's popularity, it could be the same with Nest and Angular.

Yes, its possible. There is a "routes" array in the angular.json configuration for the build target where you can tell it which routes to prerender.

I'm willing to concede that it may be a skill issue not a Gatsby issue - but I found that my builds were super slow (in the realm of 5-10 mins) and I would often run into unclear errors/issues. I also just didn't really like the general approach all that much (e.g. how GraphQL is used). My whole workflow/build process just felt very painful/brittle. SvelteKit has been quite a lot nicer, and I don't have any complaints about it. I expected to like using SvelteKit more than I actually did - in general it works great and my builds are way faster now and the codebase much simpler. But I still find myself wanting to use Angular (even though I know it has nowhere near the SSR/SSG support of SvelteKit right now, but I'm hoping it moves toward that and I am willing to suffer a bit of pain along the way, especially if I can help move the needle in that direction)

Yes it possible

I'm on a Mac and no distro but I do have my config public here: github.com/joshuamorony/nvim

nvim startup time when he wrote nvim . seemed a bit slow considering it's supposed to be this instant powerful text editor

@@JoshuaMorony awesome Joshua, thanks for sharing

I'm going to at least try to migrate to Analog - if it goes well I will switch to it in prod, and if I can't do everything I need with it then we'll still just have lots of content for the channel

thanks! and no I'm not running any black friday sales

Analog is a separate (and community created) thing - generating a new Angular SSR app will not bring in Analog you would have to specifically use Analog. As to your second question I don't know, I'm not familiar enough with the changes yet and never really properly used universal.

Hey Jeff, thanks - really glad to hear you're enjoying it! And I haven't actually done much with code gen tools so can't really give any thoughts/advice there, it is something I'd like to learn more about though

@JoshuaMorony What do you think about adding more crud operations to the quicklist example in the course? I am somewhat insecure at that point and not sure if I should implement such operation in the reducer or as an side effect of an "action". for example calling a add/create endpoint - where is the best place to add it ? and if the endpoint returns the updated entity, where should I update the state in the signal. It would really help a lot if you could add such real world scenarios to your examples.

​@@jeffnikelson5824 the chat appliaction deals more with this full round trip of data (e.g. sending data from the app to some backend and also receiving data back from the backend). But in general - let's say hypothetically the quicklists application actually stored data in some remote backend - I would have the "add" action switch to some request to send that data to the server (e.g. a standard http.post) - this can be done in conjunction with the reducer if you like e.g this.add$.pipe(/* switch to http request /*).subscribe(etc). For getting the data back into the application I would generally also want to be streaming from the backend back into the app - so the add$ action doesn't need to worry about updating the state, it just sends the request off to the backend. The data will flow back in by you having some source that is listening for data being added to the backend/db. Of course, all of this can be adapted to specific needs, but that is my general/basic approach.

@@JoshuaMorony Thanks for the very interesting answer. I would like to go into the details on that one. Is there any way to reach out to you and have a chat ? don't know if you have a discord or similar

It's definitely coming, Nx too

Great idea 💡

SEO is much better when using SSR, so if thats important for your use case its worth considering

it user has disabled javascript they will at least see some content instead of blank page

SPAs and they default rendering mechanism (CSR) are great for client side purposes and performance, dashboards, internal apps or just apps behind a login page in general, that's where they really shine. Problem with CSR is that is has really poor rendering performance at first as it takes a lot of time to start all that JS locally + it has none SEO as crawlers can't simply parse the content inside of JS files. So usually depends on your website and overall app design, but for example you can have public side of your web in SSG or SSR so you improve your SEO, conversions and your page is ranked really good at Google and then you can have your app as SPA behind a login page so you improve local performance, smoothness and just add native look and feel for your users.

SPA is not good with SEO

SPEEEEEEEEEEEEED! If you've ever battled some heavy Angular app performance you'd know :D

Sure you can find my nvim config here: github.com/joshuamorony/nvim

Thanks a lot @@JoshuaMorony

It seems that this project isn't developed anymore

I use lazygit

@@JoshuaMorony thanks 🙏

HttpInterceptorFn don't work for this?

Not if you want to intercept the request header from the server side, HttpInterceptorFn just works from the client side. @@Dajuhf

Why would you want to do HTTP calls during *build* time? SSR is provided on top of Express. Express can pull any data you want from anywhere and pump into an Angular component.

might aswell just add #ad at the end lmfao

@@stupidddd what is #ad?

As in angular universal?