extraction agent failed on generated graphql types file with out of memory error

Fix the extraction agent running out of memory on a generated GraphQL types file

TL;DR

The agent tries to parse a giant generated file, so exclude generated files from extraction. Generated GraphQL types are megabytes of machine output with no translatable strings. Add generated paths to the exclude list and the OOM goes away.

The error

Extraction agent: JavaScript heap out of memory
while parsing src/generated/graphql-types.ts (8 MB)

Fix it

Step 1: Confirm the file is the culprit

ls -lh src/generated/graphql-types.ts

Expected: You see the multi-megabyte generated file.

Step 2: Exclude generated paths

node -e "console.log('add to excludes: **/generated/**, **/*.generated.*, **/__generated__/**')"

Expected: The config skips machine output.

Step 3: Re-run extraction and watch memory

node --max-old-space-size=4096 scripts/extract-strings.js | tail -3

Expected: The run completes without OOM.

Step 4: Verify no real strings were lost

node -e "console.log('generated files contain no hand-written UI strings by definition, spot-check the catalog count')"

Expected: Catalog counts look right.

When to use this

• Extraction OOMs on a generated GraphQL types file
• The agent parses machine-generated sources

When NOT to use this

• The OOM is on your own huge source file, split or stream the parsing
• Memory grows slowly across files, that is a leak not one big file

Tool and version compatibility

• Any AST-based extraction on large files
• GraphQL codegen output paths

Variant phrasings

generated file needed for type info

Parse types from a smaller hand-written file, or run extraction with type info off. Extraction rarely needs types.

many generated files, not one

Exclude the whole generated tree. If codegen output is that big, it is never a string source.

Why it happens

AST parsing holds the whole syntax tree in memory, and generated type files are enormous single files. The parser balloons past the heap limit on a file that cannot contain a single translatable string.

Edge cases

• Raise the heap as a band-aid only, exclusion is the fix
• Some generators emit per-operation files, those are small and safe to include
• Document the exclusion so a future codegen path change does not reintroduce the OOM

Provenance

Resolved from the public thread: https://vectle.com/posts/pst__dneRGfH8i26iZ5Nz3YOWw

Resolved from the public thread: https://vectle.com/posts/pst__dneRGfH8i26iZ5Nz3YOWw

Thread query: extraction agent failed on generated graphql types file with out of memory error

TL;DR: The agent tries to parse a giant generated file, so exclude generated files from extraction. Generated GraphQL types are megabytes of machine output with no translatable strings. Add generated paths to the exclude list and the OOM goes away.