devon
devon
RRailway
Created by devon on 3/31/2024 in #✋|help
Railway projects suddenly failing with new "Cannot find type definition file for 'mime'" Error
Seems that something changed in the Railway infra because even 'redeploying' previously working projects, I'm getting this new error during build. Any idea why redeploys suddenly error on mime types?
WARN config production Use `--omit=dev` instead.
#12 0.802
#12 0.802 > [email protected] clean
#12 0.802 > cross-env ./node_modules/.bin/rimraf dist
#12 0.802

#12 1.738 production environment using .env.production

#12 35.94 error TS2688: Cannot find type definition file for 'mime'.
#12 35.94 The file is in the program because:
#12 35.94 Entry point for implicit type library 'mime'

#12 ERROR: process "/bin/bash -ol pipefail -c cross-env npm run clean && cross-env medusa-admin build && tsc -p tsconfig.server.json" did not complete successfully: exit code: 2

-----
> [stage-0 8/10] RUN --mount=type=cache,id=s/fb3a601a-4fe9-4358-8ffd-12d303256e6e-node_modules/cache,target=/app/node_modules/.cache cross-env npm run clean && cross-env medusa-admin build && tsc -p tsconfig.server.json:
WARN config production Use `--omit=dev` instead.
0.802
0.802 > [email protected] clean
0.802 > cross-env ./node_modules/.bin/rimraf dist
0.802
1.738 production environment using .env.production
35.94 error TS2688: Cannot find type definition file for 'mime'.

35.94 The file is in the program because:
35.94 Entry point for implicit type library 'mime'
-----

Dockerfile:24
-------------------
22 | # build phase
23 | COPY . /app/.
24 | >>> RUN --mount=type=cache,id=s/fb3a601a-4fe9-4358-8ffd-12d303256e6e-node_modules/cache,target=/app/node_modules/.cache cross-env npm run clean && cross-env medusa-admin build && tsc -p tsconfig.server.json
25 |
26 |

-------------------
ERROR: failed to solve: process "/bin/bash -ol pipefail -c cross-env npm run clean && cross-env medusa-admin build && tsc -p tsconfig.server.json" did not complete successfully: exit code: 2

Error: Docker build failed
WARN config production Use `--omit=dev` instead.
#12 0.802
#12 0.802 > [email protected] clean
#12 0.802 > cross-env ./node_modules/.bin/rimraf dist
#12 0.802

#12 1.738 production environment using .env.production

#12 35.94 error TS2688: Cannot find type definition file for 'mime'.
#12 35.94 The file is in the program because:
#12 35.94 Entry point for implicit type library 'mime'

#12 ERROR: process "/bin/bash -ol pipefail -c cross-env npm run clean && cross-env medusa-admin build && tsc -p tsconfig.server.json" did not complete successfully: exit code: 2

-----
> [stage-0 8/10] RUN --mount=type=cache,id=s/fb3a601a-4fe9-4358-8ffd-12d303256e6e-node_modules/cache,target=/app/node_modules/.cache cross-env npm run clean && cross-env medusa-admin build && tsc -p tsconfig.server.json:
WARN config production Use `--omit=dev` instead.
0.802
0.802 > [email protected] clean
0.802 > cross-env ./node_modules/.bin/rimraf dist
0.802
1.738 production environment using .env.production
35.94 error TS2688: Cannot find type definition file for 'mime'.

35.94 The file is in the program because:
35.94 Entry point for implicit type library 'mime'
-----

Dockerfile:24
-------------------
22 | # build phase
23 | COPY . /app/.
24 | >>> RUN --mount=type=cache,id=s/fb3a601a-4fe9-4358-8ffd-12d303256e6e-node_modules/cache,target=/app/node_modules/.cache cross-env npm run clean && cross-env medusa-admin build && tsc -p tsconfig.server.json
25 |
26 |

-------------------
ERROR: failed to solve: process "/bin/bash -ol pipefail -c cross-env npm run clean && cross-env medusa-admin build && tsc -p tsconfig.server.json" did not complete successfully: exit code: 2

Error: Docker build failed
2158ac66-80be-42ae-b4e4-d6bbbe244d21
165 replies
RRailway
Created by devon on 3/17/2024 in #✋|help
Railway instance getting 'Error starting server' on redeploy with new (or same) environment variable
I had a Medusa backend instance running on Railway (completely fine since December). Just changed a single environment variable (was trying to add to the CORS), and then got errors on the re-deploy, and the instance never came back up. Nothing else changed. And when I change the variable back to its previous value, it also fails... I can 'rollback' and it works though. So I'm now 'stuck' with an old deploy I can't make any changes to... Can anyone interpret the deploy logs below (in the next message for length)? The build logs look fine too until the health check fails as a result of the server not starting... project id: a9d9c589-b108-418d-951e-f5817ea3bc1f Any ideas would be amazing, or let me know if more info needed...
5 replies
RRailway
Created by devon on 11/20/2023 in #✋|help
Railway not seeing updates to upstream (public) repository
No description
13 replies