Enforcing coding standards in a JS library
summary
Argues that enforcing standards increases focus and creativity and shows exactly how: a Spotify JS ad library uses editorconfig, eslint (with babel-eslint) and jscs for style/quality, gulp/babel to transpile ES6 into published ES5, mocha/karma/selenium for tests, plato to generate per-commit complexity reports, and a Jenkins pipeline plus conventional-changelog to automate releases to a private npm registry. Core team of six spends ~20% time on hack days; setup scripts and git hooks make the flow reproducible.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:35Key words
- 3:55Tools Principles
- 5:11Editor Config
- 6:44Coding Style Tools
- 15:36Git Commit Standards
- 17:24Build Tools
- 18:29ES6 Build
- 20:30Testing
- 22:08Jenkins Pipeline
- 24:13Documentation
- 25:05Docs
- 27:21Questions
related talks
31mCode Style and Violence
40mRefactoring large JavaScript codebases
58mImproving the Quality of JavaScript Code
46mThe “Perfect” JS Library Tooling
39mManaging an Open Source Project
01h 01mUseful Tools and Utils for JS Development
31mDevelopment Standards: A Step-by-Step Guide to Implementing Them Without Pain
25mWrite Perfect Code with Standard and ESLint