CHECKOUT-9388: Lazy load payment strategies by importing them on demand #2563
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
17b14c2 to
0c479dd
Compare
…ng them on demand
…ly rather than at once
0c479dd to
e472db6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What/Why?
Lazy load payment strategies by importing them on demand. This is achieved by switching to
@bigcommerce/checkout-sdk/essential, which excludes payment integration code from its distribution bundle. To initialise a payment method, we now explicitly import its corresponding integration strategy and pass it into the initialisation method. This allows us to effectively lazy load the integration code only when needed, instead of loading all strategies upfront when only a few are applicable.Rollout/Rollback
Disable
CHECKOUT-9450.lazy_load_payment_strategiesexperimentTesting
See bigcommerce/checkout-sdk-js#2989