Armen, Charles, and Lucas join this week's panelist episode. They dive deep into the process of converting components to standalones using a schematic provided by the Angular team. They discuss the challenges faced in the migration process, insights into the reasons behind certain Angular features still being module-based, and the adoption of new control flow syntax. They also share their experiences with transitioning to Angular 17, involving challenges, code changes, and a migration process that requires careful consideration. Plus, they explore the use of signals for reactive state and change detection and shed light on the migration to Angular SSR, including helpful tips and best practices.SponsorsChuck's Resume TemplateDeveloper Book ClubBecome a Top 1% Dev with a Top End Devs MembershipSocial MediaUnvoidLinkedIn @unvoidweb https://www.linkedin.com/company/unvoidwebInstagram @unvoidweb https://www.instagram.com/unvoidwebLucas PaganiniYouTube @lucaspaganiniweb https://youtube.com/@lucaspaganiniwebLinkedIn @lucaspaganiniweb https://www.linkedin.com/in/lucaspaganiniwebTwitter @lucaspaganini https://twitter.com/LucasPaganiniInstagram @lucaspaganini https://www.instagram.com/lucaspaganiniArmen VardanyanLinkedIn https://www.linkedin.com/in/armen-vardanyan-am/Charles Max WoodLinkedIn https://www.linkedin.com/in/charlesmaxwood/Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/adventures-in-angular--6102018/support.

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related