inland moth
Dealing with issues related to this and I am not sure if there is anything I can configure with railway to fix my deploys.
https://github.com/iamkun/dayjs/issues/2102
https://bugs.chromium.org/p/v8/issues/detail?id=13490
Everything seems to work fine locally so I am assuming(probably wrongly) that it has something to do with the deployment environment.
inland moth
N/A
misty hull
Looks to me like it’s a bug with the package. Unless someone suggested a working fix in the thread, there’s likely no fix
inland moth
I am not entirely sure. A build works locally fine and that thread seems to tie it back to the environment its running in. I don't however understand enough of whats going on with railway/nixpacks to understand if it makes sense.
I do agree its most likely specific to the implementation in the package but based on the comments the environment seems to have some effect. But besides changing node versions on nixpacks which didn't work I wasnt sure if there was anything else to fiddle with.
inland moth
I definitely should have included this in the original post. A build with the same version of the library works fine that I can roll back. But new builds will result in the error
misty hull
Unfortunately there’s no way to configure the linux environment, I’m not sure how to troubleshoot from here. Very weird issue. Is there another date time library you could use?
inland moth
Yea some goods options to switch it out. Just kinda using it to understand a little bit better whats going on as well. But I guess that answers most of my questions. I assume at some point this is also one of those things that once something somewhere is updated it will start working. Thanks for the help!
misty hull
No problem! Sorry I couldn’t be of more help
woven walrus