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: define react and react-dom as peerDependencies #614

Conversation

magicmatatjahu
Copy link
Member

@magicmatatjahu magicmatatjahu commented Jun 27, 2022

Description

Changes proposed in this pull request:

We use react and react-dom in component, but we don't have defined these packages as peer-dependencies and e.g. yarn throw error due to this fact. See more #609

I tested package installing new project with yarn without and with react/react-dom deps and yarn in first case throw errors, in second installation passed.

Related issue(s)
Resolves #609

@magicmatatjahu magicmatatjahu added bug Something isn't working dependencies Pull requests that update a dependency file labels Jun 27, 2022
@sonarcloud
Copy link

sonarcloud bot commented Jun 27, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@magicmatatjahu
Copy link
Member Author

@derberg ping, ping :)

@magicmatatjahu
Copy link
Member Author

/rtm

@magicmatatjahu magicmatatjahu merged commit 3660a0e into asyncapi:next Jul 5, 2022
@magicmatatjahu magicmatatjahu deleted the next-branches/react-as-peer-dependency branch July 5, 2022 12:12
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 1.0.0-next.39 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dependencies Pull requests that update a dependency file ready-to-merge released on @next
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants