We're not creating our own libraries for a couple of reasons: firstly, this was supposed to be a quick project to see if an app is viable (but has now lasted long enough that we've run into this issue), and secondly we've already got forks of key libraries, which is taking more time away from implementing actual features since we now need to maintain them and pull in updates from the original repos.
Yes we should have kept dependencies up-to-date, but constant breaking changes are just taking too much time away from development time, so it's not a good fit for our project as it stands.
I don't think you are supposed to make a production RN app out of the bat, by just using 3rd party dependencies.
RN isn't wordpress where someone can employ you and say I want this and that and then you go off install 50 plugins and thats it, your project is completed.
If you are installing a lot of RN 3rd party dependencies for a production environment then you are doing it wrong.
The best thing RN has to offer is being able to write React for parts and write Native code for heavy tasks.
You do need to go down and write your own components natively, sure if someone has done it before and its well maintained and you tested it and works for you then fine use that library, if not then don't install it but make your own.
For js components only components, then again if its very well maintained then use it, but nothing stops you for making the component that works for you.
RN is a bit less work than writing a Native app, but not too far apart. It's not meant to be for webviews and for people that just want to make a complex production app using 3rd party dependencies in very little time. Its meant for dev teams that JS is their main language but do have someone that has an understanding of native code.
That said it always depends on your usage and if it fits your purpose, but I wouldn't rely on 3rd party devs to solve my issues.