Skip to main content

Widgets Overview

A widget is a small functional unit that can be reused across multiple pages/apps. It usually covers very specific functionalities like displaying relevant information or allowing to perform common actions.

A widget cannot have its own routes, hence you cannot navigate to a widget. Widgets are meant to not change or unmount when the route changes however there is no restriction for this and the interface allows contextual widgets.

Widgets are mounted only in specific areas as defined by the Layout Widget (which is also a widget) and some areas may be hidden on certain viewports/screen sizes. For example the widget area in the current implementation of the Layout Widget is hidden on mobile devices.

Beside the central area which is used by the apps, there are other sections in the layout that can be used by widget. As an example, the sidebar, the top bar and the cards on the right of the screen are all widgets.

Examples of widgets are:

  • Trending widget showing latest profiles and trending topics
  • Topbar widget showing the World logo and buttons for navigation, authentication and sidebar toggle.
  • Mini Profile widget which shows brief overview of the beam author's profile on the full beam page

Registration

Widget registration follows the same steps as any extension registration which is documented here

info

The register function must be synchronous and defined as a named export.

The register function takes only one argument which is an object of the type IntegrationRegistrationOptions.

Configuration object interface

The config object returned returned has the IAppConfig type. The required parameters are:

export const register = () => {
return {
loadingFn: () => importPromise,
mountsIn: string,
};
};

loadingFn - defines how the application is mounted/unmounted by importing the single-spa-react lifecycle methods.

mountsIn -> the slot id of the area (defined in the layout widget) on which the widget mounts.

Contextual widgets

Route based mounting of a widget is possible using the optional activeWhen property

export const register = () => {
return {
...
activeWhen: (location, pathToActiveWhen) => {
return pathToActiveWhen('/some/path')(location);
}
}
}

The second parameter of activeWhen is a utility function. This utility function converts a URL path into an activity function which when called with the current Location, returns a boolean. The path that is passed to pathToActiveWhen can also contain dynamic values.

Example:

<!-- dynamic values -->
pathToActiveWhen(/users/:userId/profile)
✅ https://app.com/users/123/profile
✅ https://app.com/users/123/profile/sub-profile/
🚫 https://app.com/users/profile/sub-profile/
🚫 https://app.com/users/profile/sub-profile/

You can also use your own matching logic like:

{
activeWhen: (location) => {
return location.pathname === 'some/path'
}
}