[email protected] No matching version found for scheduler@^16.6.2

[imsobear]

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?

[email protected]

[janryWang]

+1

[heiniuhaha]

+1

[weepy3641]

+1

[zmh7057]

+1

[J0NNYZER0]

Just got the same

[Jonir227]

+1

[njugray]

same problem

[bloody-ux]

+1

[Godsenal]

+1

[FranklinTesla]

aha, i think this is a slip of pen of the version

[xingxinghuo1000]

hand slipped lol

[wssgcg1213]

emergency! waiting online

[teokeecheng]

Same problem~

[tknickman]

Also just ran into this

[chenmingjia]

Also just ran into this

[beyondxgb]

stupid mistake, hope to solve quickly

[panyifei]

+1，and cnpm works

[broadliyn]

Use yarn install instead of npm install for now.
You can choose scheduler version when you're using yarn.

[eddiechen1008]

+1

[tao1991123]

+1s

[uncledu]

+1

[eddiechen1008]

[email protected] › [email protected] › scheduler@^16.6.2

[dongyeo]

+1s

[liajoy]

+1

[hvangumi]

+1

[dkao1978]

+1

[liangklfangl]

+1

[sebmarkbage]

We're aware. Also, 👍 is better than +1 comments.

[eddiechen1008]

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

[yanm1ng]

same problem. waiting online

[Ahkari]

+1

[lylpixin2121]

+1

[zco4321]

+1

[daggmano]

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!!)

[yize]

+1

[SteinNs]

+1

[KPonceBP]

+1

[ZhiGang-Fang]

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

[zintaen]

+1

[jianzhichun]

+1

愁啊。。

[afc163]

Whole world are waiting SF Bay waking up. 😆

[tongbin]

+1

[ycjcl868]

+1

[HKChen]

+1

[yinfxs]

+1

[quirimmo]

Guys, stop floodding the post with useless +1 comments please.
It makes just the thread unreadable.
The issue has been reported and confirmed.

[LeoEatle]

why will this happen? I just wonder...

[EugeneNguyen]

someone make a sleepy-commit?

[ZhiGang-Fang]

The project is going online, the automation script is not available, and the repair is waiting online

[younth]

wake up and fix it !

[acdlite]

Fixed in 16.6.3 https://unpkg.com/[email protected]/package.json

[daggmano]

Farewell 16.6.2, it seems we barely knew you...

[sanketthanvi]

+1 👍

[lipeibin1995]

what happened?

[hamidra]

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:)

[zhoumh1988]

I remove the file '.evn', it works well.
or
use yarn to install.

[acdlite]

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

[webmasterdevlin]

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.

[vamisola]

update npm