Lukas

Confirm this exists for me as well, issue for me seems to be that it does not use the generated types but instead the base types from the expo router...

I can confirm this, I previously used spacetime js to simplify date comparisons in my expo managed app. With the newest release of expo 48 we transitioned to hermes engine...

Here you go:  Doing date operations on about 600 objects in an array takes 4.2s, which is extremely slow Spacetime is this lib: https://github.com/spencermountain/spacetime

Here is the same function, and results using just Date objects.  Which means this takes 4-5 frames to calculate, which is incredibly slow even that

Testing shows that creating spacetime objects is whats taking 95% of the time in hermes, so I tested it using node locally and here is the same test pretty much....

 Mine looks like this and gets the same error. I have set check to write as the docs say here:  Will have to go through and enable each...

This still exists @brentvatne. But for me this happens when using non-local modules. In my monorepo that has a expo 50 sdk app I get the same error when building....