How to tell when to create a new component?

Question

I've been looking around behind the logic of when someone shall create a new component in a web application on angularjs / angular but I suppose this is more general and might apply on all component based front end frameworks.

I know that there are some principles like it should be abstract and reusable but e.g. I have seen on angular docs that each separate route looks at a specific component (how can this be reusable). Is there any solid question which I might ask before creating a new component ?

Answer 1

In order to make a decision whether you have to create a component or not, i think you have to answer the following questions:

1. Is it possible for your code chunk to be reused? If yes, construction of a new component seems like a great idea.
2. Is your code quite complex? If yes maybe its good idea to split in separate components in order to make your code more readable and maintainable.