-
Notifications
You must be signed in to change notification settings - Fork 160
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
Making peer dependencies less strict #303
Labels
Comments
You are absolutely right. I hope to find time to do it this week, I hope it's not time-critical. |
Merged
github-actions bot
pushed a commit
that referenced
this issue
Jul 22, 2021
# [3.0.0-develop.4](v3.0.0-develop.3...v3.0.0-develop.4) (2021-07-22) ### Bug Fixes * Make peerDependencies less strict ([1c3a8f2](1c3a8f2)), closes [#303](#303)
🎉 This issue has been resolved in version 3.0.0-develop.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Thanks :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
peerDependencies
defined in the package.json file https://github.com/sebbo2002/ical-generator/blob/develop/package.json#L68-L70 are a little more strict than they really have to be.For example: I cannot use ical-generator with types from Node16 as the range defined is
^15.0.3
. Same is true withluxon
.Shouldn't we change them to accept anything greater than the supported version
>= 15.0.3
?I am using npm version
7.19.1
The text was updated successfully, but these errors were encountered: