We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
peerDependencies
Observing package.json in XCM SDK I have found out that the rules for peerDependencies are pretty strict
package.json
I would prefer to have more benevolent rules for packages
e.g: current
"peerDependencies": { "@polkadot/api": "^12.4.2", "@polkadot/api-base": "^12.4.2", "@polkadot/apps-config": "^0.143.2", "@polkadot/types": "^12.4.2", "@polkadot/util": "^13.0.2" }
ideal
"peerDependencies": { "@polkadot/api": ">= 12.4", "@polkadot/api-base": ">= 12.4", "@polkadot/apps-config": ">= 0.143", "@polkadot/types": ">= 12.4", "@polkadot/util": ">= 13" }
The text was updated successfully, but these errors were encountered:
@vikiival , added :). Thanks for the improvement suggestion!
Sorry, something went wrong.
michaeldev5
Successfully merging a pull request may close this issue.
Context
Observing
package.json
in XCM SDK I have found out that the rules forpeerDependencies
are pretty strictSolution
I would prefer to have more benevolent rules for packages
e.g:
current
ideal
Ref
The text was updated successfully, but these errors were encountered: