💻 Freelancer 💻 Passionate fullstack software developer 🅰 Angular focused 🌎 Love travelling ☕ Coffee-lover 👨👩👧 Father 🦋@michaelbe812
Stuttgart, Deutschland
Joined October 2018
- Tweets1.4K
- Following333
- Followers583
- Likes3.9K
My GitHub contributions, every year since 2017: 12,199 in total.
Generate yours: mo.rgan.co/gh/michaelbe812
Michael Be 💻🏝 retweeted
@brandontroberts is too humble, so let me clarify.
ANALOG is a NECESSITY for SERIOUS TESTING.
Not just previous Angular versions, but also for the current one and beyond.
Here's why:
✅ Analog provides the FULL Vitest ecosystem: IDE extensions, plugins, native vite.config.ts support - much more than Angular CLI offers out of the box.
✅ No lock-in: (1) Tests use the same Vitest API regardless of Analog or Angular CLI, and (2) You can keep Angular CLI for serve/dev/build while using Analog specifically for testing.
✅ Angular’s official move toward Vitest validates Analog's earlier decision. It’s no longer an 'alternative' path; it’s the standard path.
Btw., you can even see @ManfredSteyer's slight surprise when I said this in the video. He knows me as very conservative, so I wouldn't say such a thing lightly.
#Angular #Vitest
🧪 Enjoyed the conversation between @ManfredSteyer and @rainerhahnekamp about the future of testing with @angular and @vitest_dev.
Appreciated the recommendation of @analogjs for previous versions of Angular and more compatibility with IDEs.
youtube.com/watch?v=1ac9cfUj…
![[EN] Angular Moves to Vitest – What Does That Mean for Us?](https://pbs.twimg.com/card_img/2116648382890688512/y3HBdxGk?format=jpg&name=800x419)
I guess i need to switch from @claudeai to codex.
I just one shotted a problem with codex which I was working on for a while with different Opus models.
Michael Be 💻🏝 retweeted
Now, at @aiPolandConf, my colleagues @rainerhahnekamp and @wolfmanfx present the next version of #Sheriff — using AI, the config is generated for your project.
Shoutout to #astro Framework (again).
Just without any effort (only optimizing images) once gets almost everytime instant almost perfect core web vitals.
On top of that I have never experienced a framework where things just work naturally.
Michael Be 💻🏝 retweeted
Spent so much time with livestreams that I forgot to promote my article 😂
Read my latest if you're an Angular developer who looks to get the sense of working and building with LLMs, especially Gemini!
Pretty entry-level, but more complex concepts on their way in part 2 😉
ALT A promotional image for a technical talk titled "Building AI Powered Apps w/ Angular & Gemini" by Armen Vardanyan. The image features a headshot of Armen Vardanyan, a man with dark hair and a beard, wearing a brown jacket, looking directly at the camera. Text overlay includes: "Building AI Powered Apps w/ Angular & Gemini," "By Armen Vardanyan," and "v19.0+." Below the title, there are logos for Angular (two stylized blue 'A's) and a Gemini diamond logo. The word "INTERMEDIATE" is centered under the Angular logo, indicating the difficulty level. The background is a light gray/white with abstract, subtle wavy lines. The man is holding a book in the bottom right corner, partially visible, with a red spine and the words "Modern Angular" on the cover.
Now I also did it …
I let AI write most of the contents of a blog post.
Let me quickly explain the motivation behind it.
I did already create a long time ago the library @angular-kit/rx-stateful (tbh 2 years ago) but I did never properly “promote” it nor writing a detailed blog post/documentation.
Not because I thought it was not worth it. It’s quite the opposite - it’s a really helpful library I use in a lot of projects.
But I never really found the time to sit down and write properly about it. I even had the plans to write a 4 to 5 part article series about it.
So time flew and now I thought: Ok, I have not the time but somehow I still want to let you know that this thingy exist. So instead of not doing it, I let AI write a blog post - Better than nothing ;-)
So here it is: a deep-dive into rx-stateful - link below 👇
#ClaudeCode 's estimations are like mine 😅
Estimated: 2 Weeks
Crunshed it in in 2 hours :D
A few weeks ago I shipped nx-plugin-openapi - a first class integration of the popular OpenApiTools generator.
I am using the plugin in a lot of projects by myself and I am very happy with it. However I also want to use other generator with the plugin.
This is the reason why I am planning a major refactoring of the internals in the upcoming weeks which will enable that we can use any generator library (like e.g. hey-openapi) with the nx-plugin.
which generator would you like to use with the plugin?
Michael Be 💻🏝 retweeted
#Angular 20.2 is out!
🧭 Zoneless is now stable
🎞 New animations system
🧭 currentNavigation becomes a Signal
🔧 TS 5.9 + service worker updates
🚫 Still no Signal Forms - next change in v21.
Changelog 👉 github.com/angular/angular/r…
Details next week in @_ng_news
Michael Be 💻🏝 retweeted
I recall having several calls with @stephenfluin a few years ago about @ModuleFederation in #Angular. We discussed an architecture where each Micro Frontend has the same Angular version. This is a straightforward solution, as from the framework's perspective, it's more or less like lazy loading.
The Challenge: When Micro Frontends live in several repos, enforcing one single version gets quite tricky. Stephen suggested collecting metadata from those repos to detect version mismatches.
And guess what? Conformance in @NxDevTools Polygraph does precisely that. The best part: with just a few lines of TypeScript you can write your own rules to enforce whatever matters to you. Plus, the workspace graph shows how different repos depend on each other 🤯.
Sounds interesting? In this article, I’ll show how to use these features by implementing a rule for exactly this use case we discussed back then 👇
Did you know that @NxDevTools Nx Polygraph can ensure conformance across multiple repositories, such as enforcing the same Angular version? All details here 👇
angulararchitects.io/en/blog…
Last week v0.3.0 of nx-plugin-openapi was published.
This release includes a few new features:
- you can now generate multiple api clients at once. Perfect if you have a microservice environment.
- you can now customize the target-name for the Nx executor to generate the api clients
Next feature on the roadmap is to support Nx inferred Tasks and ship the plugin as a crystal plugin.
Can we instruct @claude_code do conditionally use custom slash commands on its own?