@expo-google-fonts/caveat-brush

中文文档
0.4.1发布于 2025/09/06MIT AND OFL-1.1TypeScriptCommonJS零依赖近 30 天下载 9322

Use the Caveat Brush font family from Google Fonts in your Expo app

原始使用文档
文档目录7 节
  1. Caveat Brush
  2. Usage
  3. 🔡 Gallery
  4. 👩‍💻 Use During Development
  5. 📖 License
  6. 🔗 Links
  7. 🤝 Contributing

@expo-google-fonts/caveat-brush

npm version license publish size publish size

This package lets you use the Caveat Brush font family from Google Fonts in your Expo app.

Caveat Brush

Caveat Brush

This font family contains 1 styles.

  • CaveatBrush_400Regular

Usage

Run this command from the shell in the root directory of your Expo project to add the font family package to your project

npx expo install @expo-google-fonts/caveat-brush expo-font

Now add code like this to your project

import { Text, View } from "react-native";
import { useFonts } from '@expo-google-fonts/caveat-brush/useFonts';
import { CaveatBrush_400Regular } from '@expo-google-fonts/caveat-brush/400Regular';

export default () => {

  let [fontsLoaded] = useFonts({
    CaveatBrush_400Regular
  });

  let fontSize = 24;
  let paddingVertical = 6;

  if (!fontsLoaded) {
    return null;
  } else {
    return (
      <View style={{ flex: 1, justifyContent: "center", alignItems: "center" }}>
        <Text style={{
          fontSize,
          paddingVertical,
          // Note the quoting of the value for `fontFamily` here; it expects a string!
          fontFamily: "CaveatBrush_400Regular"
        }}>
          Caveat Brush Regular
        </Text>
      </View>
    );
  }
};
CaveatBrush_400Regular

👩‍💻 Use During Development

If you are trying out lots of different fonts, you can try using the @expo-google-fonts/dev package.

You can import any font style from any Expo Google Fonts package from it. It will load the fonts over the network at runtime instead of adding the asset as a file to your project, so it may take longer for your app to get to interactivity at startup, but it is extremely convenient for playing around with any style that you want.

📖 License

The @expo-google-fonts/caveat-brush package and its code are released under the MIT license.

All the fonts in the Google Fonts catalog are free and open source.

Check the Caveat Brush page on Google Fonts for the specific license of this font family.

You can use these fonts freely in your products & projects - print or digital, commercial or otherwise. However, you can't sell the fonts on their own. This isn't legal advice, please consider consulting a lawyer and see the full license for all details.

🤝 Contributing

Contributions are very welcome! This entire directory, including what you are reading now, was generated from code. Instead of submitting PRs to this directly, please make contributions to the generator instead.

版本与发布记录

@expo-google-fonts/caveat-brush 共发布 8 个版本,首次发布于 2020/05/06;过去 12 个月发布了 0 个版本。

版本发布日期距今
0.4.1latest2025/09/061.2 年前
0.4.02025/05/281.5 年前
0.3.02025/03/311.6 年前
0.2.32023/02/223 年前
0.2.22022/01/154 年前
0.2.02021/06/305 年前

关于 @expo-google-fonts/caveat-brush 的常见问题

@expo-google-fonts/caveat-brush 是什么?

Use the Caveat Brush font family from Google Fonts in your Expo app

如何安装 @expo-google-fonts/caveat-brush?

在项目目录运行 npm install @expo-google-fonts/caveat-brush,或使用 pnpm add / yarn add / bun add。

@expo-google-fonts/caveat-brush 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@expo-google-fonts/caveat-brush 支持 ESM 还是 CommonJS?

以 CommonJS 形式发布,可以直接 require();在 ES Module 项目中也可以用 import 引入(Node.js 会把 module.exports 作为默认导出)。

@expo-google-fonts/caveat-brush 可以商用吗?

@expo-google-fonts/caveat-brush 使用 MIT AND OFL-1.1 许可。声明的许可为 MIT AND OFL-1.1,请阅读许可原文确认使用条件。以上为概括,不构成法律意见,请以许可原文为准。

@expo-google-fonts/caveat-brush 的下载量有多少?

根据 npm 官方下载统计,@expo-google-fonts/caveat-brush 在 2026/10/14 – 2026/11/12 这 30 天内被下载 9,322 次,日均约 311 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@expo-google-fonts/caveat-brush 还在维护吗?

最新版本 0.4.1 发布于 2025/09/06(1.2 年前);至今共发布 8 个版本,其中过去 12 个月发布了 0 个;首次发布于 2020/05/06。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。