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
I recently started using the expo-google-fonts package and get the following message from expo-doctor on build.
> npx expo-doctor
...
✖ Validate packages against React Native Directory package metadata
...
Detailed check results:
The following issues were found when validating your dependencies against React Native Directory:
No metadata available: @expo-google-fonts/source-sans-pro
Advice:
- Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.
I've gone ahead and suppresed the warning with the following in my package.json
but I'd like to contribute the package to this repo to resolve the issue as it recommends.
I can go ahead and put in a PR according to the docs for @expo-google-fonts/source-sans-pro, but since there's so many specific expo-google-fonts packages, I was wondering if I could add the top level repo instead, and get all of the fonts at once?
The text was updated successfully, but these errors were encountered:
I recently started using the expo-google-fonts package and get the following message from
expo-doctor
on build.I've gone ahead and suppresed the warning with the following in my
package.json
but I'd like to contribute the package to this repo to resolve the issue as it recommends.
I can go ahead and put in a PR according to the docs for
@expo-google-fonts/source-sans-pro
, but since there's so many specific expo-google-fonts packages, I was wondering if I could add the top level repo instead, and get all of the fonts at once?The text was updated successfully, but these errors were encountered: