npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-native-mo-fontlink

v0.1.19

Published

react-native automatically check and link fonts

Downloads

8

Readme

react-native-mo-fontlink

Provide font-autolinking for react-native / metro (ios and android)

Instead of fiddling with Info.plist and adding resources and checking if the font filenames are correct, simply require() or import them.

IOS

On IOS, this works by adding a custom build phase (via react-native.config.js, which requires this module to have a podspec and xcodeproj) that moves the font files in the build dir (${TARGET_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}) from assets/something/.../font.ttf to /.

All found fonts are added to Info.plist (also in the build dir).

Additionally the postscript font names are compared to the filenames. For a font to work, the filename must match the postscript name.

For IOS Simulator builds where the bundling process is skipped the bundler server is called at http://localhost:8081/index.bundle?platform=ios&dev=true and the registerAsset() calls are parsed from the bundle. The referenced fonts are then downloaded to the build dir.

Android

Android works out of the box as it seems.