Enea Jahollari
@eneajaho.me
Hyping Angular everywhere I can 🅰️ | GDE for Angular
I've seen that pattern used in a project 👀
February 19, 2025 at 9:05 AM
I've seen that pattern used in a project 👀
Sometimes you can pre-fetch!
The initial fetch can happen on the server too! SSR to the rescue!
But it's not needed for normal SPA.
For websites it's crucial!
The initial fetch can happen on the server too! SSR to the rescue!
But it's not needed for normal SPA.
For websites it's crucial!
February 18, 2025 at 2:02 PM
Sometimes you can pre-fetch!
The initial fetch can happen on the server too! SSR to the rescue!
But it's not needed for normal SPA.
For websites it's crucial!
The initial fetch can happen on the server too! SSR to the rescue!
But it's not needed for normal SPA.
For websites it's crucial!
It's the best way to introduce CLS (Cumulative Layout Shift)
So, the best thing you can do is to start fetching as soon as possible! And for that you can use the router!
Don't fetch inside ngOnInit. Fetch inside a route resolver! That's why it's there!
Move data fetching up, as much as possible!
So, the best thing you can do is to start fetching as soon as possible! And for that you can use the router!
Don't fetch inside ngOnInit. Fetch inside a route resolver! That's why it's there!
Move data fetching up, as much as possible!
February 18, 2025 at 2:01 PM
It's the best way to introduce CLS (Cumulative Layout Shift)
So, the best thing you can do is to start fetching as soon as possible! And for that you can use the router!
Don't fetch inside ngOnInit. Fetch inside a route resolver! That's why it's there!
Move data fetching up, as much as possible!
So, the best thing you can do is to start fetching as soon as possible! And for that you can use the router!
Don't fetch inside ngOnInit. Fetch inside a route resolver! That's why it's there!
Move data fetching up, as much as possible!
When do you plan to release the initial version?
February 18, 2025 at 1:40 PM
When do you plan to release the initial version?