fix: use dynamic imports for plugins construction #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Description
Users will only have the dependencies of the plugins they require. This change adds separation between plugins and their factories with dynamic imports in order to prevent errors from occurring when a user does not have a dependency required by a plugin they are not using. For example, if not using the AWS Secrets Manager plugin, the
@aws-sdk/client-secrets-manager
package should not be required.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.