Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: rm NodeJS type from core, rm react core peer #681

Merged
merged 5 commits into from
Nov 27, 2023

Conversation

toddbaert
Copy link
Member

  • remove a NodeJS type from core module which needs to be platform agnostic
  • remove core peer dep from react sdk, which gets core through web-sdk

* remove a NodeJS type from core module which needs to be platform
  agnostic
* remove core peer dep from react sdk, which gets core through web-sdk

Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
@toddbaert toddbaert requested a review from a team as a code owner November 22, 2023 16:30
toddbaert and others added 2 commits November 22, 2023 12:09
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Co-authored-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Copy link
Member

@lukas-reining lukas-reining left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!
PlatformEventEmitter seems like a good way of avoiding the bundling issue as the EventEmitter interface will also be stable enough.

@toddbaert toddbaert added this pull request to the merge queue Nov 27, 2023
Merged via the queue into main with commit 09ff7b4 Nov 27, 2023
7 checks passed
@toddbaert toddbaert deleted the fix/remove-node-type branch November 27, 2023 16:21
toddbaert pushed a commit that referenced this pull request Nov 27, 2023
🤖 I have created a release *beep* *boop*
---


##
[0.0.20](core-v0.0.19...core-v0.0.20)
(2023-11-27)


### 🐛 Bug Fixes

* add Provider Not Ready Error
([#680](#680))
([b0054f9](b0054f9))
* rm NodeJS type from core, rm react core peer
([#681](#681))
([09ff7b4](09ff7b4))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
Signed-off-by: openfeature-peer-update-bot <openfeature-peer-update-bot@openfeature.dev>
Co-authored-by: openfeature-peer-update-bot <openfeature-peer-update-bot@openfeature.dev>
toddbaert pushed a commit that referenced this pull request Nov 27, 2023
🤖 I have created a release *beep* *boop*
---


##
[0.0.5-experimental](react-sdk-v0.0.4-experimental...react-sdk-v0.0.5-experimental)
(2023-11-27)


### 🐛 Bug Fixes

* rm NodeJS type from core, rm react core peer
([#681](#681))
([09ff7b4](09ff7b4))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants