Matthieu Riegler
@jeanmeche.com
The guys who codes on the train.
Doing OSS for the Angular Fwk
Grenoble - France
Doing OSS for the Angular Fwk
Grenoble - France
What I mean is that APIs design can determine how code gets tree shaken if some specific behaviors aren’t used
October 30, 2025 at 11:35 PM
What I mean is that APIs design can determine how code gets tree shaken if some specific behaviors aren’t used
Yeah the drag and drop of the CDK is actually feature heavy and is weighs quite a lot.
Maybe it’s worth inspecting if some optimizations are still possible without impacting Dx too much.
Maybe it’s worth inspecting if some optimizations are still possible without impacting Dx too much.
October 30, 2025 at 9:58 AM
Yeah the drag and drop of the CDK is actually feature heavy and is weighs quite a lot.
Maybe it’s worth inspecting if some optimizations are still possible without impacting Dx too much.
Maybe it’s worth inspecting if some optimizations are still possible without impacting Dx too much.
October 29, 2025 at 10:15 PM
Thank you for the feedback, much appreciated !
September 15, 2025 at 8:27 PM
Thank you for the feedback, much appreciated !
August 27, 2025 at 11:56 AM
Reposted by Matthieu Riegler
@jeanmeche.com wrote an unexpectedly enlightening piece on Angular's rendering mechanics. Worth reading even if Angular isn't your cup of tea.
February 27, 2025 at 9:02 AM
@jeanmeche.com wrote an unexpectedly enlightening piece on Angular's rendering mechanics. Worth reading even if Angular isn't your cup of tea.
HttpResource isn’t meant to replace the current HttpClient. It’s purely dedicated to data fetching and representing this as state with async capabilities.
Medium/Long term I would expect that we land a new promise based HttpClient to complete the « data fetching story » without Observables.
Medium/Long term I would expect that we land a new promise based HttpClient to complete the « data fetching story » without Observables.
HttpClient.it
January 25, 2025 at 9:28 PM
HttpResource isn’t meant to replace the current HttpClient. It’s purely dedicated to data fetching and representing this as state with async capabilities.
Medium/Long term I would expect that we land a new promise based HttpClient to complete the « data fetching story » without Observables.
Medium/Long term I would expect that we land a new promise based HttpClient to complete the « data fetching story » without Observables.
TLDR: Don't expect resources to send POST/PUT/DELETE for you. Resources are meant to pull data.
January 25, 2025 at 6:16 PM
TLDR: Don't expect resources to send POST/PUT/DELETE for you. Resources are meant to pull data.