react: react@16.6.2 No matching version found for scheduler@^16.6.2
Do you want to request a feature or report a bug?
bug
What is the current behavior?
➜ npm install react@latest
npm ERR! code ETARGET
npm ERR! notarget No matching version found for scheduler@^16.6.2
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'react'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/sobear/.npm/_logs/2018-11-13T02_57_46_814Z-debug.log
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn’t have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:
What is the expected behavior?
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
react@16.6.2
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 102
- Comments: 59
Commits related to this issue
- fix: No matching version found for scheduler@^16.6.2 https://github.com/facebook/react/issues/14208 — committed to cnpm/bug-versions by fengmk2 6 years ago
- fix: No matching version found for scheduler@^16.6.2 (#21) https://github.com/facebook/react/issues/14208 — committed to cnpm/bug-versions by fengmk2 6 years ago
- Greenkeeper/monorepo.react 16.6.3 (#115) * chore(package): update react to version 16.6.3 * chore(package): update react-dom to version 16.6.3 * chore(package): update lockfile package-lock.jso... — committed to calpa/gatsby-starter-calpa-blog by calpa 6 years ago
- Bump react to version 16.6.3 to get fix invalid scheduler version Fixes this error: https://github.com/facebook/react/issues/14208 — committed to TRMW/blitzentrapper by TRMW 6 years ago
Fixed in 16.6.3 https://unpkg.com/react@16.6.3/package.json
We’re aware. Also, 👍 is better than +1 comments.
+1
same problem
Guys, stop floodding the post with useless +1 comments please. It makes just the thread unreadable. The issue has been reported and confirmed.
Just got the same
+1
+1
+1
Farewell 16.6.2, it seems we barely knew you…
Whole world are waiting SF Bay waking up. 😆
+1
Yeah we’re working on improving our release process and tooling.
We’re moving to a new release flow where all stable releases are built by downloading a previously published canary directly from npm and re-publishing it with new versions. The idea is that the stable packages should be identical to the ones in the canary.
The only difference, which we can’t avoid, is that we have to update the versions. Which is the exact thing that broke in this case 😄
Oops!
I’m going to add some snapshot tests to the release script to protect against future regressions.
I also probably slightly rushed this patch release because there were some Suspense-related bugfixes that really needed to go out. Usually we would wait for a canary build to stabilize a bit before promoting it to stable.
Thanks for your patience! And also, please use lockfiles next time 😄
By the looks of a linked issue above, is this a bug in react or in a linked library? (And seriously guys, enough with the ‘+1’ comments - they get it!!)
Use
yarn installinstead ofnpm installfor now. You can chooseschedulerversion when you’re using yarn.+1
+1
wake up and fix it !
Also just ran into this
Same problem~
Also just ran into this
emergency! waiting online
+1
same problem. waiting online
hand slipped lol
+1 👍
+1
+1
+1
+1s
stupid mistake, hope to solve quickly
+1
+1
+1
npm i react
+1s
update npm
Can you also add proper tests for dependency version sanity checks to prevent this from happening again! This type of bugs will have ripple effect:)
+1
+1
+1
Install fail! Error: [react@16.6.2 › scheduler@^16.6.2] Can’t find package scheduler@^16.6.2 Error: [react@16.6.2 › scheduler@^16.6.2] Can’t find package scheduler@^16.6.2 at resolve (/usr/local/lib/node_modules/cnpm/node_modules/npminstall/lib/download/npm.js:92:11) at resolve.next (<anonymous>) at onFulfilled (/usr/local/lib/node_modules/cnpm/node_modules/co/index.js:65:19) at process._tickCallback (internal/process/next_tick.js:68:7) npminstall version: 3.0.1
+1
+1
+1
+1
+1
+1
+1
+1，and cnpm works