Frontend architecture @ mytaxi

This is a talk about the frontend architecture at mytaxi by Leonard Koch and me. It explains how we use and structure libraries and what advantages come with it.

Transcript

1. Frontend @ mytaxi Libraries, Configurations & Experiences Jonas Reitmann @jonicious Leonard Koch @LeonardKoch_
2. Where we are • 13 Frontend Developers • ~15 Frontend Applications • ~20 internal Libraries
3. Component libraries How to not write everything twice
6. Multiple component libraries Structuring libraries is hard
7. “Internal components” A library just for internal purposes
8. “React Forms” A library just for forms and inputs
9. github.com/styleguidist/react-styleguidist
12. Learnings Things we learned
13. Configs • Webpack • ESLint • Jest We share any config we can.
14. Configs • Tend to be more unique per project because of browser requirements • Before babel 7 can’t be written in Javascript Babel configs are a special case
15. Compilation Exception: Libraries for legacy projects without Webpack. We don’t compile any of our libraries
16. Versioning Spoiler: SemVer
17. SemVer MAJOR.MINOR.PATCH
18. Break things Maybe not too often
19. Communicate changes early Others might have breaking changes as well
20. Provide a migration path Make it easy for others to use new versions
21. Thank you! Questions?