Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
React-table 5.6.0 -> 6.0.0 content no longer displayed
See original GitHub issueWhat version of React-Table are you using?
In the latest version (6.5.0), the table data and columns no longer appear. The latest version that doesn’t have this issue is 5.6.0.
What bug are you experiencing, or what feature are you proposing?
- Bug is similar to a previously reported one: #496 , and it’s happening in the latest versions of Chrome and Safari.
Screenshots
Using 6.0.0 - 6.5.0
Using 5.6.0 (works as intended)
My environment:
- Webpack: 1.12.15
- react-redux: 4.4.5
- react-router: 2.3.0
- react-router-redux: 4.0.2
The issue is that the recommended solution, which is adding <!DOCTYPE html> to the start of the HTML page isn’t a viable/proper solution for React apps (see https://github.com/facebook/react/issues/1035). For pure React apps that use react-router-redux (https://github.com/reactjs/react-router-redux) to generate pages, adding the doctype isn’t feasible (or would be hacky).
Use https://codesandbox.io/s/X6npLXPRW (by clicking the “Fork” button) to reproduce the issue.
- Was unable to reproduce in the sandbox.
What are the steps to reproduce the issue?
- Create react app with main.js entry point configured in webpack.config
- Use react-router-redux to set up routes in main.js (as shown in the getting started example here: https://github.com/reactjs/react-router-redux)
Next steps:
- For devs that can’t apply the recommended solution, downgrading to v5.6.0 should be listed in the FAQ as an alternative.
- I eventually plan on running through each commit from 5.6.0 to 6.0.0 to find which code changes are causing this issue. I’ll keep this issue updated.
Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I agree - but it works as a temporary workaround until it gets fixed (I’ll be sure to include a link to this issue).
What’s already on the FAQ isn’t a solution for some react apps (especially those using react-redux-routes) (see https://github.com/facebook/react/issues/1035) - but adding the doctype should be the first option.
Glad it helped you solve the problem in the short term. I have a feeling like you that the root of the issue is caused by faulty definition of flex in the default css. So I think this should be investigated further to see if changing the css solves the issue without causing other display errors.
My suggestion feels a bit too hacky to be part of general FAQ but that is just my opinion.