After v0.2.0 upgrade: Invariant Violation => Rename RNCMaskedView to RNMaskedView
See original GitHub issueThis issue prevents me from using react-native-masked-view v0.2.0 because I can’t run this and v0.1.10 in parallel, while the latter is a peer dependency for @react-navigation/stack ("@react-native-community/masked-view": ">= 0.1.0"
that is). Installing both yields the following error which makes sense:
Invariant Violation: Tried to register two views with the same name RNCMaskedView
This could be avoided by renaming RNCMaskedView to RNMaskedView, which makes more sense anyway, since the RNC stood for @react-native-community and this is not under the RNC umbrella anymore.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:10
Top Results From Across the Web
Developers - After v0.2.0 upgrade: Invariant Violation => Rename ...
After v0.2.0 upgrade : Invariant Violation => Rename RNCMaskedView to ... This issue prevents me from using react-native-masked-view v0.2.0 because I can't ...
Read more >Invariant Violation: Tried to register two views with the same ...
I ran into this problem when I upgraded my project using npm-check-updates. That is obviously not the correct way of doing it for...
Read more >Invariant Violation: The navigation prop is missing for this ...
Build error after upgrading to React Navigation 3. ... In v2 and earlier, the containers in React Navigation are automatically provided by ...
Read more >masked-view - githubmemory
After v0.2.0 upgrade: Invariant Violation => Rename RNCMaskedView to RNMaskedView. costerik. costerik OPEN · Updated 1 year ago ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@JimTeva I honestly don’t know how that would make any difference. It is a matter of principle. I would just like to work with the most uptodate versions of my packages, and this is preventing me from that.
To actually answer your question,
Xcode 12 compatibility
would definitely be nice. But you don’t know if this package will get a major update with some cool new feature in the near future, do you? And in that case, it would be impossible for any React Navigation integrator to use that new feature. Bummer.https://www.npmjs.com/package/babel-plugin-module-resolver