You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We may want to surface some libraries that are very widely depended on and in some cases formerly included in core, like async-storage, webview, picker, slider, and net-info so that they are very easy to discover.
Which libraries need to be surfaced?
What are some libraries that end up being depended on by most React Native apps?
What is a good way to do this?
Do we want a landing page with information like this surfaced? How do we ensure that we're not limiting the ability for competing libraries to gain adoption?
The text was updated successfully, but these errors were encountered:
We may want to surface some libraries that are very widely depended on and in some cases formerly included in core, like async-storage, webview, picker, slider, and net-info so that they are very easy to discover.
Which libraries need to be surfaced?
What are some libraries that end up being depended on by most React Native apps?
What is a good way to do this?
Do we want a landing page with information like this surfaced? How do we ensure that we're not limiting the ability for competing libraries to gain adoption?
The text was updated successfully, but these errors were encountered: