Breaking peer dependency change in minor version
See original GitHub issueIn https://github.com/brigade/react-waypoint/commit/836c24e3818f490aa2ebecf491cb9840f627918e a peer dependency on "prop-types": "^15.0.0"
was added and this change made its way into 5.3.0
. This is a breaking change and causes the following error to be thrown Uncaught Error: Cannot find module "prop-types"
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9
Top Results From Across the Web
How peerDependencies affect package versions #502 - GitHub
In an npm module, any peer dep change that removes a previously valid version from being valid is a major/breaking change.
Read more >Does updating a package dependency by a major version ...
The thing is I'm curious whether or not the new version of my package itself should be a new major version. I have...
Read more >SemVer versioning. Lifehacks on how to keep both… | ING Blog
SemVer says that a major is a breaking change, a minor is backward-compatible with new features and a patch is a backward-compatible bugfix....
Read more >Versions of dependencies - Yarn
When developers talk about two semver versions being “compatible” with one another they are referring to the backwards-compatible changes ( minor and patch...
Read more >Updating Dependencies in a Frontend Project in 6 Easy-ish ...
Step 2: Start by making updates to the latest minor version ... Dependency warnings usually alert you to unmet peer dependencies (less ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jmeas Thanks for the super quick response time on resolving this! Awesome component btw 🙂.
@JemarJones / @Deliaz , this has been published as v5.3.1. We’ll follow up with v6.0.0 momentarily with this breaking change re-introduced.
Sorry again for the trouble! 🙈