0

What do you mean " 'StyleProvider' cannot be used as a JSX component"? That was added 8 months ago. Did something change in React 16 (yup 16) in the last few days since I ran an npm i? Dammit? Now I have to go dig through commits and see what changed

Comments
  • 0
    Let's just hope it's an import error
  • 0
    Do you have native-base installed? All StyleProvider searches I did led to Native-base and react native
  • 0
    Turns out it was because a dependency got updated. The updated dependency uses React 18, we were on React 16, and they didn't want to play nicely with eachother
  • 0
    @coder-guy can you be more specific? /Which/ package got updated?
  • 1
    @melezorus34 one of our internal dependencies, Foo, bumped their React version. They bumped the bug version when bumping Foo and it busted a couple of other projects as Foo was used in multiple places. That had been backed out, Foo's major version was bumped, and we have added resolution blocks in several of our package.json's to help prevent against this in the future. We also have cards to upgrade those projects to React 18 so we can try and keep the same level across the company
Add Comment