8828489432 Fix broken web component setup in SSR environments #18
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
tebexjaames
changed the title
Contributor
|
Hey @tebexjaames could you resolve the merge conflicts? :) |
Contributor
Author
|
@Chilledson Done; just needed a rebuild :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The web component definition in
src/webComponents/TebexCheckout.tswas causing issues in a Next + Electron project since it seems to have a SSR portion where HTMLElement isn't defined. This just wraps that class definition in a function which is only called in browser environments. I made sure that theTebexCheckouttype is still exported correctly, so it should be fully backwards-compatible.