graphql-hive / graphql-hive/SOFA
How should I handle big schema?
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 91
- Avg merge
- 5h 10m
- Merged PRs (30d)
- 1
Description
I haven't figure out how to resolve this issue yet.
This libaray works fine when the schema is not too big. However, when I try to use a realworld schema it always fails at `buildSchema`. My schema is 444KB with 16K lines.
```ts
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
```
I do increase my memory to 8GB but it doesn't helps.
I am willing to make a simpler schema but it's also quite tricky to deal with the nested props and types. Any workaround or tools would be welcome
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure at buildSchema with a schema close to the reported 444KB and 16K lines, then inspect how schema construction handles nested props and types. Done should mean identifying a documented workaround, tool, or confirmed fix for the JavaScript heap out-of-memory failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, backend-api-design, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100