Closed danramteke closed 2 years ago
Verified at https://github.com/danramteke/docker-astro-slow-build/runs/4643816143?check_suite_focus=true
Is this the kind of issue that may be resolved behind our upcoming SSR flag, @matthewp?
I'll have to take a look at the example but yes, most likely it is.
Hey, this issue is out of date and may have been fixed in the latest version of Astro. If you can still reproduce the issue with the latest version of astro (npm install astro@next
) please open a new issue and we can take a deeper look. :+1:
The latest static build process, used via astro build --experimental-static-build
, should take care of this. The flag is only short term and will be swapped out as the default build process in the near future 👍
@tony-sull @matthewp @jonathantneal looks like this is not resolved using astro@next
and --experimental-static-build
Upgrade astro: https://github.com/danramteke/docker-astro-slow-build/runs/5219063956?check_suite_focus=true Upgrade all deps: https://github.com/danramteke/docker-astro-slow-build/runs/5219165788?check_suite_focus=true
I encountered a memory issue, possibly due to Decap CMS. Before running npm run build, I manually deleted the dist folder, and everything worked perfectly. To automate this, I added the following configuration to my package.json:
"clean": "rm -rf dist",
"build": "npm run clean && astro build",
What version of
astro
are you using?0.21.13
What package manager are you using?
yarn
What operating system are you using?
Mac
Describe the Bug
Small site renders fine on both my dev machines. When
astro build
runs as aRUN
step inside of a Docker build, it runs out of memory. Increasing the memory usingNODE_OPTIONS=--max_old_space_size=8192
still results in failureHere is the stack trace.
Link to Minimal Reproducible Example
https://github.com/danramteke/docker-astro-slow-build