Revisit dependency pinning
See original GitHub issuePinning all of our dependencies causes issues with the preflight check whenever a new version of a nested dependency is released. babel-jest
is one example of this. When a new version is released and used by another dependency the preflight check fails until we update our version to match.
We should consider unpinning certain dependencies like babel-jest
and updating the preflight check to work with carrot versions like ^24.7.1
. It currently only works with exact version numbers.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:18
- Comments:15 (4 by maintainers)
Top Results From Across the Web
Should you Pin your JavaScript Dependencies?
If instead you "pin" your dependencies rather than use ranges, it means you use exact entries like "foobar": "1.1. 0" which means "use...
Read more >Should I be pinning my dependencies? - Packaging
The recent threads on PEP665 got me wondering whether I should revisit my decision not to pin dependencies when I distribute Python ...
Read more >Dependency Pinning Guide - EasyPost
Dependency Pinning Guide. This guide will show you how to pin a specific version of a dependency in your application. This guide will...
Read more >To pin or not to pin dependencies: reproducible vs. reusable ...
One camp was proposing explicitly listing which version of a dependency is required (a scheme also referred to "pinning") and the other camp ......
Read more >How should you pin dependencies and why? – The Guild
Nevertheless pinning still has a big advantage even when the failure is not caught in time: instead of randomly looking for which dependency...
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
Jest 24.8.0 breaks it again.
When I run
npx create-react-app someapp
and then runyarn start
. It gave me the following error.The error went away after I changed
"babel-jest": "24.7.1"
to"babel-jest": "^24.7.1"
in package.json of create-react-app.Suffering from the very same issue. Any CRA made this morning fails to start because of 24.8.0 in babel-jest. Same output as @yuchuan1