ELIFECYCLE Command failed with exit code 137.
sarbazxTRIAL
8 months ago
Getting following error on build:
Generating import map
No new imports found, skipping writing import map
⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 15.0.0-canary.129
- Experiments (use with caution):
· turbo
Creating an optimized production build ...
✓ Compiled successfully
Linting and checking validity of types ...
⨯ ESLint: Invalid Options: - Unknown options: useEslintrc, extensions - 'extensions' has been removed.
Collecting page data ...
Killed
ELIFECYCLE Command failed with exit code 137.
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 137
exit status 137
container event container died
Stopping Container
is this because of RAM?
ⓘ Deployment information is only viewable by project members and Railway employees.
2 Replies
8 months ago
From your deploy logs -
ESLint: Invalid Options: - Unknown options: useEslintrc, extensions - 'extensions' has been removed.
sarbazxTRIAL
8 months ago
From your deploy logs -
ESLint: Invalid Options: - Unknown options: useEslintrc, extensions - 'extensions' has been removed.
that shouldn't fail the build because I can successfully build on my local machine despite the given warning
Attachments