Frontend automation: bring it to the next level
summary
Claim: automate and centralize frontend scripts by extracting automation into a separate repo; built a small proof of concept called run it that fetches remote repositories, installs their automation deps into the project and exposes tasks via npm, plus a release command that generates changelog commits and tags (npm publish commented out). Implementation uses Flow, async/await on Node >7.8 and the changelog npm module; the prototype works and is on GitHub for inspection.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:28FRONTEND AUTOMATION BRING IT TO THE NEXT LEVEL
- 1:22EVERYTHING STARTED TO CHANGE AROUND 2010
- 8:27ALWAYS EVOLVING STANDARDS
- 9:03ALWAYS EVOLVING STACK OF TOOLS
- 11:49TOO MANY UNSTABLE OPTIONS
- 13:01GROW INTERNAL EXPERTISE
- 14:47CREATE A CURATED LIST OF SKILLED INDIVIDUALS TO FOLLOW
- 15:47YOU WILL BREAK THINGS MOST OF THE TIME
- 21:49YOU SHOULD ALSO TEST YOUR PROJECT'S AUTOMATION
- 22:23ORGANIZE YOUR AUTOMATION AND DECOUPLE IT FROM THE PROJECT
- 22:56MOVE YOUR AUTOMATION TO A SEPARATE REPOSITORY
- 29:55YOUR AUTOMATION IS NEVER FINISHED
- 30:57DEVELOPER EXPERIENCE MATTERS
related talks
25mA How I learned to Stop Worrying and Let the Robot Publish to NPM
29mManaging a Large Front-End Project with Automated Build Tools
22mSetting up Enterprise Frontend for Success
45mLet's automate one more thing
50mFrontend-as-a-Service Automated Testing: Layers and CI Pipelines
19mKill all humans – Automate npm releases and dependency updates
50m360° automation with GitHub Actions
41mHandling Monorepos Today