When we have features such as method, computed or watch, that we want to use in more than one component or view, we can create and use mixins to avoid repetitive codes.

In small projects, we can create and import a mixin file for each repetitive feature (method, computed, watch,etc…) and use it. However, as the project grows, creating a mixin file for each feature will cause the mixins folder to swell. Instead of creating many mixin files, we can create a main mixin file per category. It would be a better method to create mixin files according to the scope, collect the mixins in the relevant files, and import only the necessary mixin.

mixins

We gathered computed and methods that we use in more than one component/view related to insights under mixins/insights/index.js.

We have included only the mixins we want to use as follows.

import of specific mix

Example usage in template:

Example usage in script:

At the time of writing this article, we used mixins as the best practice. However, we can improve or change solutions over time.

Originally published at insight.heybooster.ai on September 30, 2021.