question-mark
Stuck on an issue?

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.

6.9.0 causes an "Invariant Violation" error

See original GitHub issue

Describe the bug Using Cell: props => props.value causes an Invariant Violation error in version 6.9.0.

To Reproduce

Expected behavior Following semantic versioning, a MINOR version from 6.7.x to 6.9.x should not break functionality.

Codesandbox! See above.

Screenshots See codesandbox: https://codesandbox.io/s/484zn1xmw7

Desktop (please complete the following information):

  • OS: MacOS 10.12.6
  • Browser chrome
  • Version 71

Smartphone (please complete the following information): NA

Additional context Our project has "react-table": "^6.8.6", in package.json, so in 6.8 it was working as intended, but when the change was made 3 days ago in 6.9.0 it stopped working. I expect this to be the case in many more projects that follow a similar upgrade pattern from package.json

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:6

github_iconTop GitHub Comments

1reaction
ddsr17commented, Jul 24, 2019

Still the issue persists, version - 6.10.0

1reaction
velika12commented, Feb 22, 2019

Unfortunately still having this issue in 6.9.2.

Read more comments on GitHub >

github_iconTop Results From Across the Web

6.9.0 causes an "Invariant Violation" error · Issue #1244 - GitHub
Describe the bug. Using Cell: props => props.value causes an Invariant Violation error in version 6.9.0. To Reproduce.
Read more >
Invariant Violation error during testing react component which ...
This gives me the following error: Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function ...
Read more >
`new nativeeventemitter()` requires a non-null argument. - You ...
ERROR Invariant Violation: Module AppRegistry is not a registered ... A frequent cause of the error is that the application entry file path...
Read more >
Active questions tagged react-native+typescript - Stack Overflow
Next React Native Bottom Navigation Error using TypeScript ... Previous Invariant Violation: requireNativeComponent: "RNSVGSvgViewAndroid" was not found in ...
Read more >
Troubleshooting common React Native bugs - LogRocket Blog
Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found