Justin McLellan

@Jean__Meche So you’re saying we can call the signal update method directly in the template now?

Arrow function support are bound to land next month in #Angular 21.2. Wrote my first one today, It felt ... like you know 😁

@DeborahKurata @dashlane Oh yeah I just stick to Dashlane every where now.

@theNEXlevel @dashlane Google password manager.

I've been using @dashlane for years, but since they removed web access, I've been SO frustrated! I don't want their browser extension (especially because it automatically turns off my google extension). There is now no way to access Dashlane on my computer. :-( Suggestions?

Powered by AI, Crexi Vault uses intelligent automation to convert OMs, flyers, and rent rolls into clean, searchable records—helping brokers list faster, analysts save time, and investors act with confidence. 🔑 Crexi Vault: AI-powered. Searchable. Streamlined. Built for the pace of #CRE. Get Started: bit.ly/3L1hXyq

@joerjohnson @CREXinc @Techweek_ Had a great time and met some awesome people. Thanks again for the invite!

It’s inspiring to hear stories from companies like @CREXinc that invest in their DX and to see the productivity benefits they achieve. Tom and @theNEXlevel shared their story today @Techweek_ in NY.

@DeborahKurata @DanielGlejzner Yeah and that’s the definitely even better. Can’t use it yet in production since it’s experimental but will be our default when it’s dev preview.

@theNEXlevel @DanielGlejzner Have you seen the new resource API? Retrieve data directly into a signal with no subscribe required!

Me when seeing .subscribe without any unsubscribe mechanism in 2025

Save the date for #ngconf like you've never experienced it! Sign up for our email for early exclusive info! #Angular #ngconf2025 📨 bit.ly/41vKHnw

@Armandotrue @DanielGlejzner Did you give the isolatedModules a shot with it yet? Curious how it went. On a side project it went fine for me but not on an enterprise level lol.

Speaking of #Angular articles... ...remember my thread on migrating a huge Angular application to standalone? Well, I converted it to an article with further more details and hints! It's in review and will soon drop. Hope you'll find it helpful 😉

@DanielGlejzner Idk I’m really liking the ergonomics of signal stores.

Good morning to everyone except those who are forcing hot new solutions into codebases just because they're "popular." 🌞🌞🌞

@Armandotrue It’ll give you another 15-30% reductionon your build time. It does require a specific declarative coding style to work though because of a single typescript pass. blog.angular.dev/using-isolated…

@theNEXlevel Hmm, to be honest I've never heard about that configuration...

Update: I finished migrating a very complex Angular app to standalone. I also migrated it to esbuild instead of webpack. End results: 18 hours spent, some improvements also made to the CI pipeline (build time down from 17 minutes to 3.5 minutes). Lessons learned, some bugs still lurking, but will be found

@DanielGlejzner Oh I’m interested!

Hey Founders, CEOs, CTOs, Tech Leads. I’m working on a very interesting initiative - if you are interested in education and/or networking + want to learn more leave a comment or DM me directly. Thanks :)

@DanielGlejzner Yeah signals make mental model and code flow so much cleaner. I love it!

@theNEXlevel Need. Now. I love my pure singles components

I think the sentiment is clear on this one 😄 #angular

@DanielGlejzner Rather not create a method*

@DanielGlejzner I disagree with this one. Rather not create a class that just calls a service method. The extra layer doesn’t make sense to me nor does it provide any benefit. Also using signal store selectors directly in the template is the way to go.

Services should be private & readonly. #angular

@DanielGlejzner @Enea_Jahollari @brechtbilliet I still prefer the single source of truth for forms which reactive gives us but then again with signals I find it much easier to work with template driven.

@Enea_Jahollari @brechtbilliet I have to work with reactive most of the time 😂

Template driven forms >>>>>> Reactive forms Don't ask me to work with very dynamic reactive forms!! I don't want to subscribe to every possible observable there is to make something work.

@Enea_Jahollari For spreading inputs I’ve been doing the transform method with the input being Partial and spreading there. But it is definitely very verbose.

If Angular gets a new authoring format, I’d like to have a couple of things to become possible: 1. Better content projection 🙏 If you have worked with Angular to build a design system, you probably have struggled to compose things easily, looking at you , ngProjectAs or having to deal with TemplateRef or s, ngTemplateOutlet and ng-containers. Understanding all of these things makes you an Angular internals expert (don’t oppose me here please), but does it have to be this way? The other thing is, we have two ways to do content projection today. And both lack either DX [ng-template, ngTemplateOutlet, ViewContainerRef] or extensibility [ng-content, ngProjectAs, select], and most of the time you’ll have to fight for the type-checking part of both [good luck with the ng-content one]. 2. Allow constants to be used in the templates Angular always lacked the possibility to import something and use it directly in the template. Having to create a class field for each constant really sucks [even though Webstorm makes it easy and creates it for you]. Also, if you don’t use it anymore in the template, you still have to remember it in the class, which most of the time you forget to do so. If the IDE is not powerful enough to know it’s not used anywhere, good luck with non tree-shakable unused fields. Angular doesn’t have to be different from other fwks/libs here, and should really enable us to not care about these things anymore. It shouldn’t be compiler magic imo, but just normal javascript variable usage. 3. Don’t make it harder for me to create a component and repeat it’s name everywhere Writing a component from scratch without the CLI shouldn’t be painful. I don’t want to remember to make the file-name, cmp selector and class name the same. Allow me to use the same name everywhere. I don’t want to check for both the selector usages and class name usages when I want to check where my component is used. 4. Support Input spreading {…someInputs} I understand why we don’t have this one, but if we’re getting a new authoring format, please, please, please, make this possible! Creating high-order components would really feel good with this one. If you want to create a button component [even with an attribute selector], good luck passing a lot of options to it without breaking a sweat. 5. Make it easy to understand what role the attributes play in the template If you pass an attribute to an element in an Angular template, how do you know if it is: - a component selector - a directive selector - a content projection selector - or just a dumb attribute ? That’s why sometimes is hard to have auto imports in Angular templates, because attributes can be anything. In my opinion, a new authoring format shouldn't be focused on class vs function topic, but what problems do we want Angular to solve for us, and maybe we can start giving ideas on how to fix those. [Half of our code is already just functions anyway] Think of it as we did for the new control flow, Angular ditched the {#if} to give life to @if . And, I believe that was the right decision, and that one came from the community. Let's start thinking outside the box to fix our issues, in ways that Angular can be here for the next 10 years, as these changes won't come immediately, looks like a 10 year plan at least to me. Thanks for reading my opinion in a Saturday 🤗 #angular

@julienrenaux This happened to me the other day and turned out to be an import from '.’ Caught it in a unit test at least though.

Only Angular developers can understand how painful this is to debug 😂