@feature-hub/core

@feature-hub/core

Create scalable web applications using micro frontends.

Allows dynamic loading of micro frontends, lifecycle management of micro frontends, and controlled sharing of state and functionality between micro frontends.

Installation

Using Yarn

yarn add @feature-hub/core

Using NPM

npm install @feature-hub/core

---

Copyright (c) 2018-2019 SinnerSchrader Deutschland GmbH. Released under the terms of the MIT License.

Changelog

2.0.0 (2019-06-20)

Bug Fixes

• all: do not destroy Feature App when it is rendered multiple times (#512) (bf8a8ad), closes #505
• all: remove all deprecated interfaces (#510) (7df042e)
• history-service: reorder createRootLocation params (#511) (92d6070)

Features

• all: let featureAppId be defined by the integrator (#504) (2565f0c), closes #495
• all: pass full env to beforeCreate callback (#506) (abeb26a), closes #490
• async-ssr-manager: move timeout from config to options (#499) (9536ef7)
• core: remove ability to provide configs via FeatureServiceRegistry (#500) (388b9f0)
• history-service: rename primaryConsumerUid to primaryConsumerId (#502) (49fae65)
• react: do not re-throw render errors on server (#508) (4b1c53e)

BREAKING CHANGES

• all: FeatureAppManager#getFeatureAppScope has been replaced by FeatureAppManager#createFeatureAppScope, since now a new FeatureAppScope is created for every call. When a Feature App is unmounted, the release method (previously called destroy) must be called. Only when all scopes for a Feature App ID have been released, the Feature App instance is destroyed.
• history-service: The currentRootLocation and consumerLocation parameters of createRootLocation have been switched.
• all: The following interfaces have been removed:
  • AsyncSsrManagerV0
  • ExternalsValidatorLike
  • FeatureAppManagerLike
  • FeatureServiceRegistryLike
  • HistoryServiceV0
  • FeatureHubContextValue
  • SerializedStateManagerV0
  • ServerRequestV0
• react: When the FeatureAppContainer/FeatureAppLoader catches a render error on the server, this error was previously re-thrown. To re-create this behavior, an onError prop must be defined that throws the error.
• all: Instead of passing the featureAppId and the featureServices as separate arguments to the beforeCreate callback, the full Feature App environment, that contains the featureAppId and featureServices, is now passed as a single argument (env). This is the same argument that is passed to the Feature App's create method.
• all: The option featureAppConfigs has been removed from the options of createFeatureHub and from the options of the FeatureAppManager constructor. The env that is passed to a Feature App's create method does not include an instanceConfig property anymore. If a Feature App must be configured, the integrator needs to specify the config prop of the FeatureAppLoader or FeatureAppContainer. Furthermore, the FeatureAppLoader or FeatureAppContainer now require a featureAppId prop, and the instanceConfig and idSpecifier props have been removed. The same applies to the <feature-app-loader> and <feature-app-container> custom elements. Since the integrator now needs to define the ID of a Feature App, the Feature App definition must not specify an id anymore.
• history-service: The option primaryConsumerUid of createRootLocationTransformer has been renamed to primaryConsumerId.
• core: The option featureServiceConfigs has been removed from the options of createFeatureHub and from the options of the FeatureServiceRegistry constructor. The env that is passed to a Feature Service's create method does not include a config property anymore. If a Feature Service must be configured, a factory function that accepts options, and that returns a Feature Service definition, should be used instead, see @feature-hub/async-ssr-manager for an example.
• async-ssr-manager: The asyncSsrManagerDefinition has been replaced with the factory function defineAsyncSsrManager. This function accepts options to set the timeout, which previously had to be set by the integrator via Feature Service configs. This is in preparation of an upcoming breaking change that removes the ability to provide Feature Service configs through the Feature Service registry.
• core: The type params of the following interfaces have been changed:
  • FeatureAppDefinition
  • FeatureAppEnvironment
  • FeatureServiceProviderDefinition
  • FeatureServiceEnvironment