styleguide | living style guide exporting React components | Frontend Framework library

To allow long lines become shorter to make more free room on small screens.

In your example:

This problem can be viewed at different angles.

If you are asking about a pure-angular architecture approach/solution, then my answer would be - yes, create a Dashboard module and import Heroes module into it. Dashboards in particular have natural tendency to adopt more and more data as they grow, very likely from yet different modules, not only Heroes. So this would be a scalable solution.

However there is another approach...

Whenever the concept of sharing data among modules arises, it is very legit to start thinking of using some kind of state management (such as ngrx.io). The main purpose of having an app-level state is to be able to share data and have a centralized, single source of truth. You would benefit a lot when your app grows app. It is scalable and doesn't require architectural changes just for the sake of being able to interchange data.

For the purpose of having a dashboard I can hardly imagine a better solution.

Your HTML file has no

presence_of_element_located expected condition finishes and the program continues to the next call while the element already created but still not clickable and still not located on it's final position on the page and still not ready to accept regular click.
JavaScript click can handle this kind of click, however this doesn't really imitates real UI user action.
To mimic real user action you should use element_to_be_clickable expected condition and click the element only when it became clickable.
visibility_of_element_located didn't work because the element is not actually visible itself, so we had to use element_to_be_clickable expected condition.
It is also possible that element is covered by some other element during the page rendering when it is literally become clickable but the page is still rendered. In this case we have to add some hardcoded delay or to wait until the element covering the desired button is disappeared. this can be achieved by invisibility_of_element_located expected condition for the covering element.

Just add a setState before your return statement

That error is a TypeScript error, not a JavaScript or single-spa error. Here are options for what you need to do:

1. Publish your utility module to a registry (types are optional since TS can infer from the source, though types are better). Then install it into each other microfrontend's node_modules. Since it's a webpack external, the version in node_modules will only be used for typescript compilation but not for execution in the browser.
2. You could publish only the types, whether as an individual package or together with other microfrontend's typings.
3. Mock the utility module's types, as described here.

Source:

• https://github.com/single-spa/single-spa/issues/609#issuecomment-665132965
• https://github.com/single-spa/single-spa.js.org/issues/361#issuecomment-737259914

I found two possible solutions:

CDN

Due to the way C++ grammar works, instead of something like foo, you can say class foo: