Speaker Q&A
summary
Panel Q&A delivers concrete, actionable answers: use npm init to scaffold an Nx monorepo and expect cyclic dependencies when migrating many apps, prefer Nx over Lerna for lighter orchestration; feature flags work well via LaunchDarkly or CMS-driven toggles and must be removed after full rollout to avoid dead code; share env via DI using a forRoot config pattern per library; no ready-made partial-checkout tool outside Google, strict-compile errors after first build is a bug worth filing, and practical migration scripts plus human-networking advice are provided.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:33Where Do You Keep Feature Flags Can You Give a Few Examples of Best Practices for these Flags
- 4:54How To Overcome Guilty of Talking
- 7:09How Do You Handle Anxiety of Accidentally Doing One of the Don'ts
- 8:46Is It Possible To Structure a Monorepo in a Way That You Can Check Out Only Part of It or a Specific Library from within the Project
- 10:02Feature Toggles
- 12:23What Headless Cms Is Delta Using and Do You Recommend that Cms
related talks
51mSpeakers Panel
26mNx for Angular Developers
22mSetting up Enterprise Frontend for Success
09mUsing Nx: Angular CLI Power-ups for Modern Development
40mNx - Enter Enterprise Development for Angular
36mHow to scale up your angular projects like a pro
20mWhat and Why nx 20 reasons in 20 minutes
40mDriving Your JavaScript Library Ecosystem With Nx