Navigating the Sea of Javascript tool
summary
Team builds a micro-frontend product called Embed ID and runs CI/CD with GitHub Actions to publish to npm, using SonarCloud and FOSSA for static and dependency scans, Jest plus Selenium for tests, and semantic-release for automatic versioning. Development favors trunk-based with feature flags; releases occur roughly twice weekly and one dedicated engineer handles tech debt in a 15–20 dev group (~1/15). Goal is shorten lead time toward under an hour.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:17Welcome
- 2:54Agenda
- 3:43The problem
- 6:28Continuous integration
- 8:45Triggering workflows
- 11:46Picking the right tools
- 12:26What languages are you using
- 14:05Trunkbased or branchbased
- 16:36Choosing a library
- 19:13Testing
- 24:39Endtoend ownership
- 27:04Summary
related talks
39mManaging an Open Source Project
36mEnforcing coding standards in a JS library
17mElevating Developer Experience at the Speed of Sound
43mScalable Best Practices for Your Development Team
01h 01mUseful Tools and Utils for JS Development
18mAutomating All the Code & Testing Things with GitHub Actions
29mManaging a Large Front-End Project with Automated Build Tools
26mLightning Branches - A Way to Supercharge Your Feature Delivery