Introducing Flow BasePacks
These reusable libraries of useful actions and components are generally used by other, more specific Flow tools.
There will be one for Actions and one for ScreenComponents. This is being done because there are really good reasons to put the Actions in a Managed Package but it’s currently impossible to create libraries of LWC’s in Managed Packages and access those LWC’s from an LWC that isn’t in the same namespace. Splitting them up does the trick.
FlowActionsBasePack
FlowActionsBasePack is a managed package. This makes it easier to install (details below).
FlowScreenComponentsBasePack
FlowScreenComponentsBasePack is an unlocked package. This is necessary because Lightning Web Components can’t use custom libraries yet if they’re managed (and thus have their own namespace)..
FlowScreenComponents BasePack requires the presence of FlowActions BasePack, because some of the screen components inside of it rely on Apex classes that are included in FlowActions BasePack. So you’ll need to install FlowActions BasePack first.
Legacy Information
There is an older FlowBaseComponents that is now obsolete, and we do not recommend the use of it as a prerequisite in new development. The existing FlowBaseComponents package version 1.3.4 will remain available for use with components that require it. We’re going to be encouraging extension developers to make use of these new base packs, going forward, and don’t plan to enhance FlowBaseComponents
Going forward, we’re breaking FlowBaseComponents into two packages: