search

rpl / flow-coverage-report

Generate flow coverage reports in JSON, HTML and in the console.
MIT License
505 stars 42 forks source link

Unpin dependencies #122

Closed IanVS closed 4 years ago

IanVS commented 7 years ago

Because this project uses pinned dependency versions, it's very likely that consumers will end up with multiple versions of various dependencies like React. React doesn't like to have multiple versions, and in some cases this is causing me problems.

I think it would be better to use semver and specify only the minimum required versions, and allow proper dependency resolution. You can check in a package.lock or yarn.lock file to ensure that consistent versions are used during development, if you like. But I don't think it's a good idea to pin dependencies as you have in your package.json.

turadg commented 6 years ago

@rpl what is your opinion on this request? Solving is as easy as merging #169

kangax commented 5 years ago

would love to see #169 merged; getting warnings about outdated react version in our project

rpl commented 4 years ago

On master all the dependencies are now unpinned (changes introduced in #197), I'm going to release it soon as a new major release. I'll keep this issue open until the new version has been released on npm.

rpl commented 4 years ago

Released on npm as part of v0.8.0