withUniwindConfig overriding unstable_enablePackageExports for web?

[pk1m]

react-native: 0.81.5
expo: 54.0.25
uniwind: 1.3.0

hello! something i noticed recently while debugging why package exports weren't working properly.

i enabled unstable_enablePackageExports within the resolver block in my metro.config.js but metro was not using "browser" condition for my libs when running on web. if i remove with withUniwindConfig from my metro.config the "browser" condition is correctly used. "react-native" condition works as expected though.

haven't had time to create a separate repro repo yet, so asking here if this is something you are aware of.

thank you!

[Brentlok]

We're not aware of it, I was curious so I've made a simple test

{
    "private": false,
    "name": "testing-lib",
    "version": "1.6.0",
    "type": "module",
    "exports": {
        ".": {
            "types": "./types.d.ts",
            "react-native": "./rn.ts",
            "browser": "./browser.js",
            "default": "./module.js"
        }
    }
}

// browser.js
export const test = 'browser'

// module.js
export const test = 'module'

// App.tsx
import { test } from 'testing-lib'

console.log(test)

And this is a result:

Everything is working as expected, so we need a minimal reproduction in order to help

[pk1m]

hey thanks for the quick reply, i tried creating a minimal reproduction but it worked as expected. and now i on my main repo its working 😅. might have been some cache issue. thanks for taking a look!