Angelo Di Santo

Engineering Manager

[Matthieu Riegler @Jean__Meche]

.@AlanAgius4 has been doing some amazing work at optimizing NPM package sizes for #Angular v19.

@angular/core 44 MB ↘️ 14MB

For ~400K downloads per week (for v18), that's 12 TB spared each week!

[Angular @angular]

Great news! The Angular CDK and Material Components are fully standalone and support hydration. Find out more here https://t.co/4Cjg3V988t

[Tomas Trajan @tomastrajan]

🛠️ The new upcoming #Angular "application" builder based on #esbuild is great!

This weekend I have managed to migrate my main project @omniboard_dev to use

@angular-devkit/build-angular:application

and the results have been amazing...

~39% faster builds!

1/2

[Minko Gechev @mgechev]

Spent hours debugging unwanted horizontal scrollbars?

@FirefoxDevTools shows directly in the inspector, which is the element with scrollbar and what are the overflowing elements 🤯

[Daniel Glejzner @DanielGlejzner]

Frontend Unit Tests.

🟡 The Gold Standard 🟡

Everyone racing for top coverage.
But reality looks much much different.

When NOT to Write Frontend Unit Tests:

• PoCs/MVPs: Here today, irrelevant tomorrow.
• UI part that is changed a lot: Don't waste your time.
• Experimental features: Can change any minute.
• Basic static components: Not worth it.
• Overwhelming mocking: Value > Effort.
• Deadlines: Especially in startups.
• Limited resources: Business value first/early phase.
• Redundant scenarios: 100% coverage is not the goal.
• Backend is more important: Frontend is changing much more often.

When TO Write Frontend Unit Tests:

• Critical features: Some things just can't fail.
• Complex logic: Once stable of course.
• Reusable components: The Foundation.
• Regression prevention: When it breaks often.
• Set in stone features: Worth the effort.
• Documentation: Tests can be great for that.
• Pre-refactoring: Before embarking on refactoring.
• Integration points: Vulnerable places.

Business Perspective:

• User Focus: E2E reflecting customer experience.
• Cost Efficiency: E2E tests can catch critical bugs.
• Time Savings: Reducing emphasis on unit tests can speed up development cycles.
• Real-world Relevance: E2E tests in near-production environments offer tangible insights.
• Simplified Reporting: E2E results are often more digestible for non-technical stakeholders.
• Coverage Overkill: Extensive unit tests can be redundant with a strong E2E suite.
• Maintenance Overhead: Frontend changes might require frequent unit test updates.

Businesses often lean towards ROI.
E2E tests often provide clearer value.

[NestJS @nestframework]

💡 2023 @StackOverflow Developer Survey results are out!

We are thrilled to announce that @nestframework made it to the top 10 most popular backend frameworks in the world 🎉

Thanks to everyone in the community who participated in the survey! ❤️

https://t.co/OHUhmKhBaj

[Angelo Di Santo @Angelo_Di_Santo]

@Lik04ka Congratulations and all the best for your new adventure 😉

[Younes Jaaidi @yjaaidi]

😱 Seriously!?

🅰️ @Angular 16.0
🐬 @NxDevTools 16.0
⚡️ @QwikDev 1.0

... the same week!

... feels like a spoiled kid overwhelmed by all the christmas gifts

[Younes Jaaidi @yjaaidi]

👀 Did you know that legacy #Angular material components will be dropped in Angular 17?

Don't panic! There is a migration schematic that will help you migrate 🪄

😉 don't wait for Angular 17, maybe it's time to migrate

👉 https://t.co/Nm3yIPkEvZ

[Manfred Steyer @ManfredSteyer]

Today, I showcased #Angular's new #Signals with a lot of live coding:

☑️ Data Binding with Signals and OnPush
☑️ Signals and (Im)mutables
☑️ Computed, Effects and glitch-freeness
☑️ Interop with RxJS and NGRX
☑️ Outlook to Signal Components

[Daniel Glejzner @DanielGlejzner]

I have written another summary for you.

👉 Signals RFC is closing on April 24th! Say something now or never!

🔥 Minko is talking about already established vision for #Angular 16 & 17

👀 #RxJS , pipes, directives fully optional?

https://t.co/8KydIhvY6n

[Angelo Di Santo @Angelo_Di_Santo]

@davidwalshblog @SaveToNotion #Tweet #osx #utilities

[Minko Gechev @mgechev]

We just landed hydration in Angular! You can try it in the prerelease of v16 on Wednesday 🔥

- No flicker due to rerendering when using SSR
- Better Core Web Vitals. 45% improvement in LCP based on early testing

https://t.co/pFSlEWAj2d

[Minko Gechev @mgechev]

📣 The Angular Signals RFC is live! We're expecting so many exciting discussions on GitHub which will shape the future of Angular!

Find the main RFC below and follow the links to dig into a particular topic 👉https://t.co/DcAW68eP7j

You can learn and comment on everything about:
‣ Signals as a reactive primitive
‣ New way to develop components with reactive inputs and simplified lifecycle hooks
‣ RxJS interoperability
‣ Much more!

#AngularMomentum

[Fernando @Franc0Fernand0]

I've never met a software engineer knowing every technology, library, or language.

It's ok to learn certain things only at a high level or not at all.

It's better to be competent in at least one area than not even be proficient in any area.

[Minko Gechev @mgechev]

Don't want to hype folks up too much but...if you thought v15 was big, v16 will seem massive!

Expect improvements in SSR, reactivity, also we'll ship some of the most popular feature requests in the framework repo 🤫

[Minko Gechev @mgechev]

Angular Momentum 🔥

[Minko Gechev @mgechev]

I'm expecting v16 to be very well hydrated...

[Minko Gechev @mgechev]

In @FirefoxDevTools you can use a visual editor to adjust CSS clip-path of an element!

Love such small features, just like the visual controls for flexbox and grid in @ChromeDevTools 🔥

[Minko Gechev @mgechev]

Tip: *only* using CSS you can apply styles to a number input conditionally depending on whether its value is within our out of range 🤯