We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm run build
171.2 ✓ 3652 modules transformed. 181.0 rendering chunks... 209.5 209.5 <--- Last few GCs ---> 209.5 209.5 [17:0x7f942ed69000] 175252 ms: Scavenge (interleaved) 2033.1 (2086.2) -> 2031.8 (2087.2) MB, pooled: 0 MB, 143.76 / 0.00 ms (average mu = 0.236, current mu = 0.194) allocation failure; 209.5 [17:0x7f942ed69000] 177665 ms: Mark-Compact 2034.5 (2087.2) -> 2031.8 (2096.7) MB, pooled: 0 MB, 2382.02 / 0.00 ms (average mu = 0.182, current mu = 0.138) allocation failure; scavenge might not succeed 209.5 209.5 209.5 <--- JS stacktrace ---> 209.5 209.5 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory 209.5 ----- Native stack trace ----- 209.5 210.6 npm error path /app 210.6 npm error command failed 210.6 npm error signal SIGABRT 210.6 npm error command sh -c npm run pyodide:fetch && vite build 210.6 npm error A complete log of this run can be found in: /root/.npm/_logs/2024-10-21T20_52_30_463Z-debug-0.log
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The text was updated successfully, but these errors were encountered: