Address Security Alerts

GitHub Content • GitHub Release • Diff

NOTE: This release is a non-breaking change (i.e. no API was affected).

• Security: Address potential security vulnerabilities in dependent libs (mostly devDependencies completely unrelated to deployment)!

feature-u V1 Integration

GitHub Content • GitHub Release • Diff

NOTE: This release contains breaking changes from prior releases (i.e. a retrofit of client code is necessary).

• Added/Removed: Eliminate singletons in favor of creators

  The singleton: logicAspect, has been replaced with a new creator: createLogicAspect().

  This is useful in both testing and server side rendering.

• Review: Integrate to feature-u V1

  feature-u V1 has replaced the app object with a fassets object.

  In general, this is not a change that would normally break a plugin, because app/fassets is a positional parameter that is merely passed through the plugin.

  However, because feature-redux-logic auto injects the [Fassets object] as a dependency in your logic modules (promoting full [Cross Feature Communication]), the logic modules in your application code must reflect this change by renaming this named parameter from app to fassets, and utilize the new fassets API accordingly. Please refer to the [Usage] section for examples.

  As a result, this plugin has now updated it's feature-u peerDependency to ">=1.0.0".

Establish Polyfill Strategy

NOTE: This release is a non-breaking change (i.e. no API was affected).

• Review: A new policy is in affect where polyfills are the responsibility of the client app, when the target JavaScript engine is inadequate (such as the IE browser). Please refer to Potential Need for Polyfills for more information.

  As a result, all previous code patches related to es2015+ polyfill issues were removed, in favor of polyfilling at the app-level.

• Internal: The most current babel version/configuration is now used to transpile the library's es5 distribution.

Initial Release

This is where it all began ...