Planning a Front-end JS Application
summary
First step is verifying a working, stable API-first design, then follow a 16-step plan before writing code so the app is built to last. Pick GitHub, Slack, Trello, npm and bower for packages, Node.js hosting (Modulus), gulp for builds, Segment.io for analytics, and plato for complexity checks. Automate tests and deploys via continuous integration and favor functional testing with Nightwatch + BrowserStack because those catch the user-facing bugs unit tests miss.
AI-written summary · about
chapters (8)
- 0:00Start
- 11:14create a foundational specification
- 16:44select host platform & hosting service node.js & modulus
- 16:57select package managers npm & bower
- 19:25select a task runner gulp.js & plugins
- 25:35define deployment strategy Cl using travis-ci
- 26:55select package monitoring solution gemnasium
- 28:45select performance monitoring solution
related talks
40mFRONTEND CHOICES
01h 07mModern Frontend Engineering
34mHow to build front-end web apps that scale
29mLean Frontend Development
49mScalable Best Practices for Your Development Team
25mPrinciples for Scaling Frontend Application Development
23mFront-End Platform Engineering
19mBuild a Frontend for Your Web App: From Basic HTML to JS Frameworks