-
Notifications
You must be signed in to change notification settings - Fork 46.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
react@16.6.2 No matching version found for scheduler@^16.6.2 #14208
Comments
+1 |
2 similar comments
+1 |
+1 |
+1 |
Just got the same |
+1 |
same problem |
+1 |
+1 |
aha, i think this is a slip of pen of the version |
hand slipped lol |
emergency! waiting online |
Same problem~ |
Also just ran into this |
1 similar comment
Also just ran into this |
stupid mistake, hope to solve quickly |
+1,and cnpm works |
Use |
+1 |
+1s |
+1 |
enzyme-adapter-react-16@1.7.0 › react-test-renderer@16.6.2 › scheduler@^16.6.2 |
+1s |
+1 |
1 similar comment
+1 |
+1 |
愁啊。。 |
Whole world are waiting SF Bay waking up. 😆 |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Guys, stop floodding the post with useless +1 comments please. |
why will this happen? I just wonder... |
someone make a sleepy-commit? |
The project is going online, the automation script is not available, and the repair is waiting online |
wake up and fix it ! |
Fixed in 16.6.3 https://unpkg.com/react@16.6.3/package.json |
Farewell 16.6.2, it seems we barely knew you... |
+1 👍 |
what happened? |
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:) |
I remove the file '.evn', it works well. |
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 |
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. |
* 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.json 值得注意的是: React 16.6.2 會 build 錯誤,因為 No matching version of scheduler@^16.6.2 ``` 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 ``` facebook/react#14208
update npm |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
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
The text was updated successfully, but these errors were encountered: