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
{{ message }}
Repository navigation
[bug]: Invalid package.json exports configuration causes Metro bundler warning #1600
The wildcard exports patterns in package.json cause Metro bundler (used by Expo/React Native) to produce warnings about non-existent files.
Warning Message
WARN The package /Users/.../node_modules/algoliasearch contains an invalid package.json configuration. Consider raising this issue with the package maintainer(s).
Reason: The resolution for "/Users/.../node_modules/algoliasearch/dist/lite/builds/browser.js" defined in "exports" is /Users/.../node_modules/algoliasearch/dist/lite/builds/browser.js.js, however this file does not exist. Falling back to file-based resolution.
Root Cause
The following wildcard exports patterns in package.json are causing the issue:
When Metro resolves ./dist/lite/builds/browser.js, the wildcard pattern ./dist/lite/builds/* captures browser.js as the * portion, and then substitutes it into ./dist/lite/builds/*.js, resulting in ./dist/lite/builds/browser.js.js — which doesn't exist.
Hey @hayata-suenaga
Do you have a minimal repro project please?
I can't manage to get the same warning than you, even if I understand the issue, and I would like to check I'm not doing any mistake before fixing it
I can put together a minimal repro tomorrow. In the meantime, you should be able to reproduce the issue by initializing any new Expo project and installing algoliasearch in it.
Activity
Kungpowpow commentedon Dec 7, 2025
+1
Fluf22 commentedon Dec 9, 2025
Hey @hayata-suenaga
Do you have a minimal repro project please?
I can't manage to get the same warning than you, even if I understand the issue, and I would like to check I'm not doing any mistake before fixing it
hayata-suenaga commentedon Dec 11, 2025
I can put together a minimal repro tomorrow. In the meantime, you should be able to reproduce the issue by initializing any new Expo project and installing
algoliasearchin it.ottob commentedon Mar 10, 2026
Any updates on this one?