[Support Request]: Status of Expo config plugin release (prebuild fails on 0.19.0)

オープン
  • 何か問題がありますか？
#711 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 5 日以内に返信

@jokerttu がすでに取り組んでいます。

2026年11月8日 から。

評価

この issue はまだ評価されていません。

説明

Summary

I'm trying to set up this package in an Expo app by following EXPO.md on main, but npx expo prebuild fails with the latest npm release (0.19.0) because that version doesn't include the config plugin.

From what I can tell, the plugin was added in #709 after v0.19.0 was published, and is waiting to ship in release PR #710 (0.19.1). npm view still shows 0.19.0 as latest, and the installed package has no app.plugin.js or plugin/ directory.

Questions
  1. Is there an expected timeline for publishing 0.19.1, or anything blocking #710?
  2. Until then, is there a supported way for Expo apps to use the plugin, or should we wait for the release?
  3. Could EXPO.md state the minimum package version that includes the plugin? It's linked from the README on the default branch, so anyone following it today will hit this error.
Environment
@googlemaps/react-native-navigation-sdk 0.19.0
Expo SDK 58.0.23
React Native 0.88.1
React 19.3.0
Node 22.20.0
OS Windows 11
Platform tested Android (npx expo prebuild -p android)
Steps to reproduce

  1. Install the package with npx expo install @googlemaps/react-native-navigation-sdk expo-build-properties.

  2. Add the plugin to app.json, as described in EXPO.md:

    "plugins": [
  "@googlemaps/react-native-navigation-sdk",
  ["expo-build-properties", { "android": { "kotlinVersion": "2.3.21" } }]
]

  3. Run npx expo prebuild -p android.

Actual result
PluginError: Transform failed with 1 error:
node_modules/react-native/index.js:27:7: ERROR: Unexpected "typeof"

No "app.plugin.{js,cjs,mjs,ts,cts,mts}" file was found in "@googlemaps/react-native-navigation-sdk", so the package's main entry was loaded instead. Config plugins are typically exported from an "app.plugin.js" file in the package root.

The No "app.plugin..." file was found line looks like the actual problem. With no plugin file, Expo falls back to the package's main entry, which pulls in react-native. The Unexpected "typeof" part appears to be a side effect: my app.config.ts imports tsx/cjs, so esbuild tries to transform React Native's Flow source. I don't think it indicates a separate bug in this package.

Expected result

npx expo prebuild finds the config plugin and generates the native projects, as EXPO.md describes.

Thanks for adding Expo support, and to @kota113 for the original work in #577.

主要言語
TypeScript
スター
226
フォーク
39
平均マージ
1日 20時間
マージ済み PR（30日）
7

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

googlemaps/react-native-navigation-sdk のほかの issue

googlemaps/react-native-navigation-sdk の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。