Describe Component Libraries

In order to reuse components across apps, it is suggested to use component libraries. Also, while using a component library, an app maintains dependencies on the components being used. The app maker will be alerted when the updates to dependent components become available. Hence, all new reusable components should be created within the component libraries instead.

 While we create components inside an app, we can also create a library of components that can be reused. Therefore, by creating a component library, app makers easily share and update one or more components with other makers.

In layman terms, component libraries are containers of component definitions that make it simpler to discover and search components, publish updates as well as notify app makers of available component updates.

Functionalities of Component Library

• Firstly, we can create a new component library or edit an existing component library from the same interface. Then, browse to make.powerapps.com, select Apps, and then select Component Libraries.
• Secondly, post creating a component library and publish, apps can consume the components from this component library by importing the library. 
• Thirdly, we can modify an existing component library and save the changes made with additional version notes. But, the updated component library version must be published for use in existing apps that use the component library.

Component Library Permissions

• Firstly, you must share a component library works the same way you share a canvas app.
• Secondly, when we share a component library, we allow others to reuse the component library.
• Thirdly, once the component library is shared, others can edit the component library and import components from this shared component library for creating and editing apps.
• Lastly, in case it is shared as a co-owner, a user can use, edit, and share a component library but not delete or change the owner.

Component Library Limitations

• Firstly, we can’t import components using a component library from locally saved component library files.
• Secondly, we can’t add existing component libraries to a solution. But, we can still create new component libraries for solutions using add component library flow.
• Thirdly, when we import a component from a component library, we can’t edit it inside the consuming app.
• Lastly, when a component is added to an app from the component library and the theme of the app is updated, the component becomes a local app component.