[email protected] 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?
imsobear
All 59 comments
+1
janryWang
on 13 Nov 2018
+1
heiniuhaha
on 13 Nov 2018
+1
weepy3641
on 13 Nov 2018
+1
zmh7057
on 13 Nov 2018
Just got the same
J0NNYZER0
on 13 Nov 2018
+1
Jonir227
on 13 Nov 2018
same problem
njugray
on 13 Nov 2018
+1
bloody-ux
on 13 Nov 2018
+1
Godsenal
on 13 Nov 2018
aha, i think this is a slip of pen of the version
FranklinTesla
on 13 Nov 2018
hand slipped lol
xingxinghuo1000
on 13 Nov 2018
emergency! waiting online
wssgcg1213
on 13 Nov 2018
Same problem~
teokeecheng
on 13 Nov 2018
Also just ran into this
tknickman
on 13 Nov 2018
Also just ran into this
chenmingjia
on 13 Nov 2018
stupid mistake, hope to solve quickly
beyondxgb
on 13 Nov 2018
+1，and cnpm works
panyifei
on 13 Nov 2018
Use yarn install instead of npm install for now.
You can choose scheduler version when you're using yarn.
broadliyn
on 13 Nov 2018
+1
eddiechen1008
on 13 Nov 2018
+1s
tao1991123
on 13 Nov 2018
+1
uncledu
on 13 Nov 2018
[email protected] › [email protected] › scheduler@^16.6.2
eddiechen1008
on 13 Nov 2018
+1s
dongyeo
on 13 Nov 2018
+1
liajoy
on 13 Nov 2018
+1
hvangumi
on 13 Nov 2018
+1
dkao1978
on 13 Nov 2018
+1
liangklfangl
on 13 Nov 2018
We're aware. Also, 👍 is better than +1 comments.
sebmarkbage
on 13 Nov 2018
npm i react
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
same problem. waiting online
yanm1ng
on 13 Nov 2018
+1
Ahkari
on 13 Nov 2018
+1
lylpixin2121
on 13 Nov 2018
+1
zco4321
on 13 Nov 2018
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!!)
daggmano
on 13 Nov 2018
+1
yize
on 13 Nov 2018
+1
SteinNs
on 13 Nov 2018
+1
KPonceBP
on 13 Nov 2018
Install fail! Error: [[email protected] › scheduler@^16.6.2] Can't find package scheduler@^16.6.2
Error: [[email protected] › 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 (
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
ZhiGang-Fang
on 13 Nov 2018
+1
zintaen
on 13 Nov 2018
+1
愁啊。。
jianzhichun
on 13 Nov 2018
Whole world are waiting SF Bay waking up. 😆
afc163
on 13 Nov 2018
+1
tongbin
on 13 Nov 2018
+1
ycjcl868
on 13 Nov 2018
+1
HKChen
on 13 Nov 2018
+1
yinfxs
on 13 Nov 2018
Guys, stop floodding the post with useless +1 comments please.
It makes just the thread unreadable.
The issue has been reported and confirmed.
quirimmo
on 13 Nov 2018
why will this happen? I just wonder...
LeoEatle
on 13 Nov 2018
someone make a sleepy-commit?
EugeneNguyen
on 13 Nov 2018
The project is going online, the automation script is not available, and the repair is waiting online
ZhiGang-Fang
on 13 Nov 2018
wake up and fix it !
younth
on 13 Nov 2018
Fixed in 16.6.3 https://unpkg.com/[email protected]/package.json
acdlite
on 13 Nov 2018
Farewell 16.6.2, it seems we barely knew you...
daggmano
on 13 Nov 2018
+1 👍
sanketthanvi
on 13 Nov 2018
what happened?
lipeibin1995
on 13 Nov 2018
Fixed in 16.6.3 https://unpkg.com/[email protected]/package.json
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:)
hamidra
on 13 Nov 2018
I remove the file '.evn', it works well.
or
use yarn to install.
zhoumh1988
on 13 Nov 2018
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 :D
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 :D
acdlite
on 13 Nov 2018
Thanks for fixing this issue, Andrew. We were in the middle of a React workshop when we encountered the bug. Glad everything is fine again.
webmasterdevlin
on 13 Nov 2018
update npm
vamisola
on 14 Nov 2018
Related issues
jimfb
·
3Comments
jvorcak
·
3Comments
UnbearableBear
·
3Comments
zpao
·
3Comments
jmullo
·
3Comments
Most helpful comment
Fixed in 16.6.3 https://unpkg.com/[email protected]/package.json