You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More a point of discussion/idea rather than a concrete feature request. If this is not the direction Configu wishes to go in then please feel free to close this issue
Several popular (large) Node libraries are split into multiple plugin-style packages, where users can choose which plugins they require. We could split the node package by config store, thus enabling users to choose which stores they require support for.
Motivation
With an ever increasing number of config store providers, the SDK's dependency tree will continue to increase going forward. This leads to:
Increased dependency resolution time
Increased likelihood of version incompatibilities with other packages
Increased installation time (particularly impacting CI/CD workflows & dependency caching)
As far as I'm aware users will typically only require a single type of config store, in some cases at most 2-3 types. Thus most users won't actually require the ability to support all config store types.
Context
Other projects that package their dependency in a similar way include:
Suggestion
More a point of discussion/idea rather than a concrete feature request. If this is not the direction Configu wishes to go in then please feel free to close this issue
Several popular (large) Node libraries are split into multiple plugin-style packages, where users can choose which plugins they require. We could split the node package by config store, thus enabling users to choose which stores they require support for.
Motivation
With an ever increasing number of config store providers, the SDK's dependency tree will continue to increase going forward. This leads to:
As far as I'm aware users will typically only require a single type of config store, in some cases at most 2-3 types. Thus most users won't actually require the ability to support all config store types.
Context
Other projects that package their dependency in a similar way include:
The text was updated successfully, but these errors were encountered: