Skip to content
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

error decoder website not displaying any messages for error codes #10838

Closed
jharris4 opened this issue Sep 26, 2017 · 5 comments
Closed

error decoder website not displaying any messages for error codes #10838

jharris4 opened this issue Sep 26, 2017 · 5 comments

Comments

@jharris4
Copy link

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

bug

What is the current behavior?

visiting https://facebook.github.io/react/docs/error-decoder.html?invariant=149 does not show the error message

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/ebsrpraL/).

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?

MacOS 10.13 / Chrome 61

@aweary
Copy link
Contributor

aweary commented Sep 26, 2017

Hey @jharris4, I'm seeing an error message on the page you linked

Element ref was specified as a string ([missing argument]) but no owner was set. You may have multiple copies of React loaded. (details: https://fb.me/react-refs-must-have-owner).

Are you seeing something different?

@gaearon
Copy link
Collaborator

gaearon commented Sep 26, 2017

We should probably the message bold or something. It's easy to miss.

@aweary
Copy link
Contributor

aweary commented Sep 26, 2017

@gaearon good call, maybe even style it as a redbox so it's even easier to see?

@jharris4
Copy link
Author

jharris4 commented Sep 26, 2017

There error message is showing now.

It really was not there when I filed the issue though, I even tried refreshing, clearing cache, changing the error code in the url etc.

Maybe I just caught it during an update related to the React 16 release or something?

@aweary
Copy link
Contributor

aweary commented Sep 26, 2017

@jharris4 there as a brief period after React 16 was launched where the CDN URLs we were using for the docs site were invalid. This was resolved by #10837. You probably visited the site during that period of downtime 👍

@aweary aweary closed this as completed Sep 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants