Skip to content

Commit ab308c8

Browse files
binnodonclaude
andcommitted
Fix GitHub Actions memory issue
- Split build steps for better error visibility - Add npm caching for faster builds - Use npm ci for reproducible installs - Increase Node.js heap size to 4GB with NODE_OPTIONS - This should fix exit code 134 (out of memory) error Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
1 parent d99a514 commit ab308c8

1 file changed

Lines changed: 12 additions & 3 deletions

File tree

.github/workflows/deploy.yml

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,21 @@ jobs:
2323
- uses: actions/setup-node@v4
2424
with:
2525
node-version: 22
26+
cache: 'npm'
2627

2728
- name: Install dependencies
28-
run: npm install
29+
run: npm ci
2930

30-
- name: Build registry and site
31-
run: npm run build:all
31+
- name: Build registry
32+
run: npm run build:registry
33+
34+
- name: Build registry index
35+
run: npm run build:registry-index
36+
37+
- name: Build site
38+
run: npm run build
39+
env:
40+
NODE_OPTIONS: --max-old-space-size=4096
3241

3342
- name: Upload artifact
3443
uses: actions/upload-pages-artifact@v3

0 commit comments

Comments
 (0)