fix: web exports on prepare file

[migueldaipre]

Summary

Fixes #2401

Fixes error in prepare.ts file that imports hasTouchableProperty from a '.' file.

It's probably related to the way ESM works, I'm not sure. I base it on PR

(0 , _.hasTouchableProperty) is not a function 
TypeError: (0 , _.hasTouchableProperty) is not a function 
at prepare

Test Plan

Should work without error on web

web-working.mov

Compatibility

OS	Implemented
Web	✅

Checklist

• I have tested this on a web project

[a-eid]

this worked for me. patched the package for now. thanks @migueldaipre

[brycnguyen]

Can we merge this?

[jakex7]

Hey @migueldaipre, thanks for sharing that! It looks good, however before we proceed with the merge, I’d like to gain a deeper understanding of the issue to prevent similar problems in the future. Could you share a repository where this issue can be reproduced? I’m not encountering it on our web-example.

[brycnguyen]

I'm currently using webpack for my expo project and ran into this issue

[idrisssakhi]

this fix is highly important for apps supporting web and having last version of react native with new-arch activated.
would you merge it please we are blocked. and i can't patch in my mmonorepo. the patch is applied but generated bob files are not re-generated after patch causing issue

[brycnguyen]

this fix is highly important for apps supporting web and having last version of react native with new-arch activated. would you merge it please we are blocked. and i can't patch in my mmonorepo. the patch is applied but generated bob files are not re-generated after patch causing issue

Until it is fixed, what I did was I cloned this repo, made the changes locally, ran the build command to generate the /web folder and replaced that in my yarn patch directory of this library.

[idrisssakhi]

@migueldaipre thank you for this great work. Is it possible to fix the conflicts ?
@jakex7 it's purely a typescript issue, adding a tsc check on next versions will help avoid such issue

[migueldaipre]

Hey @migueldaipre, thanks for sharing that! It looks good, however before we proceed with the merge, I’d like to gain a deeper understanding of the issue to prevent similar problems in the future. Could you share a repository where this issue can be reproduced? I’m not encountering it on our web-example.

Hey there, I haven't had time to create a repro and the current project is private and large. But that's just down to how the code is imported, when I use “.” the error happens, when I change to “./index” the error doesn't happen.

[G2Jose]

Anything we can do to get this in soon? I'm running into this issue as well.

[bastdus]

Same here. It's been broken since version 15.5 on the web.

Downgrade to 15.4 until it's fixed.

[G2Jose]

Here's a patch you can use with patch-package based on this Pull Request until it's merged