Why not move all configs into a separate package and reduce boilerplate to zero?
summary
Describes extracting ESLint, Babel, Webpack and other tool configurations into separate themed npm packages to eliminate per-project boilerplate and reduce package.json clutter. Explains the approach the Beeline team used to replace many dependencies with a single import and recounts unexpected problems they encountered while implementing it.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 7:49Frontend evolution
- 16:53Config problems in monorepo
- 25:07Distributed monolith transition
- 36:37Config support and optimization
- 47:10Pros and cons of config center
- 55:00Architecture recommendations
- 1:00:19Q&A
