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
https://reactnative.directory is a listing of React Native community projects, catalogued with interesting project metadata like repo popularity/activity (stars, forks, issues) and usage (monthly npm downloads).
See if there is an opportunity to leverage this data in dep-check, in partnership with reactnative.directory.
Can we use it as-is to make dep-check better?
Should we augment the data to include compatibility info (something we can curate, but that package authors can also publish on their own)?
If we decide to pursue this, do it in the open using the rnx-kit website and GitHub issue tracker. Incorporate it into the rnx-kit website docs.
There was some initial interest but no one is moving this forward. Leaving it on the backlog. We can probably make a framework that Expo will like if we put the work in, and if they can fit their internal data (they have this mapping already) into it.
During AppJS Brent actually gave us an interesting update, there's an ongoing PR to basically do the first fundamental step in this, meaning scraping from the rnx-kit config the versions: react-native-community/directory#838
tido64
changed the title
Investigate a partnership between dep-check and https://reactnative.directory
Investigate a partnership between align-deps and https://reactnative.directory
Nov 11, 2022
https://reactnative.directory is a listing of React Native community projects, catalogued with interesting project metadata like repo popularity/activity (stars, forks, issues) and usage (monthly npm downloads).
See if there is an opportunity to leverage this data in dep-check, in partnership with reactnative.directory.
If we decide to pursue this, do it in the open using the rnx-kit website and GitHub issue tracker. Incorporate it into the rnx-kit website docs.
Originally posted by @kelset in #1328 (comment)
The text was updated successfully, but these errors were encountered: