Sharing Top Content from the Angular-sphere.

Yep, JavaScript Moves Fast. Build Your Component Library Anyway.

  • Here’s a question I’ve heard a few times recently: – “What if we create a component library in React/Vue/Angular/whatever and a new component technology replaces it?”
  • Without a component library, your team is highly likely to include duplicate JavaScript that solves the same problems in slightly different ways which will bloat the bundle and slow performance.
  • The advantage to this approach is twofold: – If you move to a new technology in the future, the plain CSS foundation that you’re using behind the scenes in your JavaScript components can be reused.If your company is currently using multiple component approaches such as React, Angular, and/or Vue, then…
  • Leverage an existing JavaScript component library as your foundation to minimize the amount of code you need to write to get rolling.
  • SummaryDon’t let the rapid innovation in JavaScript scare you away from investing in a reusable component library for your company.

That’s not a question of if. It’s a question of when. These technologies have become wildly popular, but they’re not the end game. Like all technologies, something better will eventually come along…

Here’s a question I’ve heard a few times recently:

“What if we create a component library in React/Vue/Angular/whatever and a new component technology replaces it?”That’s not a question of if. It’s a question of when. These technologies have become wildly popular, but they’re not the end game. Like all technologies, something better will eventually come along and replace them.

But that fact is largely irrelevant. Establishing a library of reusable components for your company today remains absolutely critical.

Here’s why.

Move Faster TodayReusable components help your team move faster by creating higher level abstractions. Components eliminate decision fatigue by programmatically enforcing a standardized approach. Just consider an opinionated form TextInput component.

It can eliminate all the following decisions:

Should I put the label above the input or beside it?Should I display validation errors to the right or below the input?What color should the error be?How should I mark required fields?Should I validate required fields on blur or upon submit?How much padding should I place between the label and the input?The list goes on. These aren’t questions your designers and developers should be asking every time they create a new form.

Enforce ConsistencyReusable components enforce user interface consistency. Your company likely has many developers. Yet your job is to build an app that looks like it was built by one developer.

To do that, it’s critical to use reusable components. Copy/paste isn’t a design pattern. If designers…

Yep, JavaScript Moves Fast. Build Your Component Library Anyway.