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
I have a repo with around 7 apps and bunch of packages but sometimes the EAS actions (or a simple expo install within an app directory) fail with the commands being unable to find a .map file.
Error: ENOENT: no such file or directory, open /Users/something/app/packages/utils/build/module/formatDateDefault.js.map
It is kinda of weird because I can see the file being there on my filesystem. When the actions fail with the same issue, I can usually resolve it by simply running that action again and then it works.
Does anyone else experience this?
The text was updated successfully, but these errors were encountered:
I am building the app thru the workflow actions which I haven't changed and are the same as seen in this repo. Should I build in EAS before starting the workflow actions?
One thing you can try is also building the packages inside EAS. With that, you should be confident all build output is available when building the app.
You can add a Build lifecycle hook, specifically the eas-build-post-install script. If you add something like this to your app's package.json, it should build the repository before building your app.
"scripts": {
"eas-build-post-install": "yarn workspaces run build"
}
I have a repo with around 7 apps and bunch of packages but sometimes the EAS actions (or a simple expo install within an app directory) fail with the commands being unable to find a .map file.
It is kinda of weird because I can see the file being there on my filesystem. When the actions fail with the same issue, I can usually resolve it by simply running that action again and then it works.
Does anyone else experience this?
The text was updated successfully, but these errors were encountered: