Closed eslawski closed 3 months ago
Latest commit: 9f29170b4547e49636d5c3e5497b316b13b3866c
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Path | Size |
---|---|
packages/pharos/lib/index.js | 64.63 KB (0%) |
Closing as we found a workaround. This issue will go away with React 19 where web components are supported out of the box
Here is the diff for the generated React component after these changes (PharosButton as an example):
To use this as a consumer it would look something like the following:
Other thoughts:
PharosContext
in thereThis change: (check at least one)
Is this a breaking change? (check one)
Is the: (complete all)
What does this change address? A clear and concise description or a direct link to an issue [e.g. #15] If adding a feature, a rationale for its addition goes here.
How does this change work? A clear, detailed description of how this change addresses the issue. This could be a bullet list if there are several moving parts.
Additional context Add any other context here.