React: react error looking for schedule@^0.5.0

[dptoot]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Installing 16.5.2 seems to throw and error looking for schedule@^0.5.0 which doesn't exist

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:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for schedule@^0.5.0
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'

What is the expected behavior?

React should get installed.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
[email protected]

[bvaughn]

Not sure what's going on– maybe a transient NPM registry issue– but [email protected] has definitely been published to NPM. You can see it here and here.

Also, both the JSFiddle and Code Sandbox you linked to work fine 😄 so I'm going to assume this was just an NPM/cache hiccup.

[dptoot]

I appreciate you looking into it. Yes. I think it may have been a caching issue within our npm proxy. Sorry for wasting some time! Thanks again.

[ghaskins99]

I think it happened again... (installing latest [email protected])
Sorry if you guys already know about this, or if this is a useless comment (16.6.2 published 37 minutes ago) ^_^

[RulerOf]

We're experiencing the same thing right now, exactly the same error text as @GraydonHaskins. I suggest adding a thumbs-up to his post above for others who are Googling their way in here.

Final edit: The issue referenced in the above comment has been resolved with the release of [email protected]

Edit:

Workaround is to edit your package.json to pin version 16.6.1 of the affected react components, or do it via the command line. For us, the following components were required:

npm install --save-exact [email protected]
npm install --save-exact [email protected]

[ryanab]

I just installed [email protected] seems to work in the interim.

[twilio-jyoung]

i get the same issue with [email protected]. 16.6.1 worked for me as well.

[matt-meyer-nyc]

I've got the same problem with scheduler@^16.6.2

I did npm install [email protected] and it's still not working.

For those that got it to work, did the command also require --save?

Thanks!

[twilio-jyoung]

i updated the reference in package.json to point to the specific version.

"dependencies": {
...
"react": "16.6.1",
"react-dom": "16.6.1"
...
},

[fyodorVS]

twilio-jyoung, this worked for you?

[ma3505]

Experiencing this same issue when using create-react-app.

[andrewquartey]

I'm experiencing the same issue. Installing [email protected] didn't work.

[ryanab]

I also installed [email protected] FYI

[matt-meyer-nyc]

No. When I did create-react-app my-app it didn't install 'package.json' ... it installed 'package-lock.json'

Which I've never seen

Ryan...you needed --save with it though, right?

[Shannor]

So for me what ended up working was two steps. First I updated package.json to
"dependencies": {
...
"react": "16.6.1",
"react-dom": "16.6.1"
...
},

Then when I ran npm install, it complained about 'react-test-renderer' next.
So I install that with 'npm install --save-exact [email protected]'
That ended up letting me do npm install for my entire project afterwards.

Hopefully that helps.

[ryanab]

@matt-meyer-nyc I did use save..try deleting react from (or if you want the entire) node_module dir as well.

[marcusevari]

Thanks @Shanno, that worked for me

[andrewquartey]

i updated the reference in package.json to point to the specific version.

"dependencies": {
...
"react": "16.6.1",
"react-dom": "16.6.1"
...
},

This worked for me

[RulerOf]

For folks having trouble, either edit package.json manually or use --save-exact with your npm command, otherwise it'll auto-upgrade to the broken version:

npm install --save-exact [email protected]
npm install --save-exact [email protected]

[nabilfikri]

i updated the reference in package.json to point to the specific version.

"dependencies": {
...
"react": "16.6.1",
"react-dom": "16.6.1"
...
},

This one worked for me

[andrewquartey]

I also installed [email protected] FYI

oh yes got it

[vijitail]

Any reason why latest react version not working?

[matt-meyer-nyc]

Hmmmm...super weird??

Maybe they're tinkering with some code?

I deleted the whole thing, and the file that it was in, and tried again.

And it's working now...I'm running:

"react": "^16.6.3", "react-dom": "^16.6.3"

[vijitail]

@matt-meyer-nyc You tried create-react-app?

[matt-meyer-nyc]

Yes. I used create-react-app and it worked.

[Shannor]

Yeah it looks like they fixed it with the 16.6.3.

[benuklove]

I was having this problem too. No matching version found for scheduler@^16.6.2.
Just ran
npx create-react-app react-tutorial and it worked this time. Edit: (16.6.3)

[quyngokms]

This module is used by react-test-renderer (and by enzyme-adapter-react-16). Explicitly declare this module will help:
npm install --save-dev [email protected]

[lednhatkhanh]

Confirm that it has been fixed

[adilmalik393]

Also had the same issue. Changing in my package.json like following worked
changing from
"react": "^16.6.1", "react-dom": "^16.6.1",
changing too
"react": "16.6.1", "react-dom": "16.6.1",

[AlejandroRodriguezP]

i decided to wait and tried to use create-react-app and its working again!

[fyodorVS]

Confirmed, it works!

[zemacnica]

npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected]

this version is published on npm

[gaearon]

https://unpkg.com/[email protected]/

You're probably behind some npm mirror.

---

I'm locking this thread since the original issue was resolved and now it attracts misinformation.