I keep running into this problem every time I try to start my Gatsby development server. The issue started happening right after I added the gatsby-source-figma plugin to my gatsby-config.js file.
The error message I’m getting is:
Missing onError handler for invocation 'building-schema', error was 'Error: Type with name "FigmaELLIPSE" does not exists'. Stacktrace was 'Error: Type with name "FigmaELLIPSE" does not exists
It seems like there’s some kind of schema building issue where Gatsby can’t find or create the FigmaELLIPSE type. Has anyone else encountered this same problem? I’m not sure if this is a configuration issue on my end or maybe a bug with the plugin itself. Any suggestions on how to fix this would be really helpful.
Classic integration headache - I’ve been there way too many times. Those manual fixes work, but they’re just bandaids.
Stop wrestling with plugin versions and cache clearing every time something breaks. I automated this whole thing using Latenode to build a rock-solid pipeline.
Connect directly to Figma’s API, process the data however you want, and output clean JSON files to your project. No schema conflicts since you control the entire data structure.
Mine triggers automatically when designers update Figma files. Validates data, handles errors smoothly, and pings me on Slack when something needs fixing.
Best part? Transform ellipse data into whatever format works for your Gatsby build. No more GraphQL type inference headaches.
This error happens when your Figma file has inconsistent states during the build. I hit this same issue during a design system migration - some ellipse nodes got corrupted or lost their metadata. The plugin can’t figure out the types when it runs into these broken shapes. Quick fix: add a nodeFilter option to your plugin config and temporarily exclude the problem elements. Set it to skip ellipses for now so you can pinpoint what’s causing it. Also check your Figma file for grouped ellipses or components with broken references. Sometimes it’s not the individual shapes that are the problem - it’s how they’re nested in frames or components.
I faced a similar issue with the gatsby-source-figma plugin as well. The FigmaELLIPSE error often arises due to the plugin’s inability to process specific Figma node types when inferring the schema. A solution that worked for me was to implement a createTypes function in the gatsby-node.js file. This approach allows you to proactively define your schema types, preventing Gatsby from making incorrect assumptions. Alternatively, consider temporarily removing any ellipse shapes from your Figma document, start the Gatsby development server without them, and then gradually reintroduce them. This method can help identify if a particular ellipse object is causing the issue.
had this exact issue last week! update your gatsby-source-figma plugin to the latest version - that’s what fixed it for me. older versions have bugs with shape node types. also check if your figma file is too complex, sometimes it chokes on too many elements.
The error you’re encountering typically occurs when the Figma plugin attempts to create GraphQL types before Gatsby has completed registering all node types. I’ve experienced the same issue previously. Ensure that you have added both gatsby-plugin-sharp and gatsby-transformer-sharp to your gatsby-config.js, as these are essential for image processing. Additionally, verify your Figma access token permissions and ensure the file you are sourcing indeed contains ellipse elements. If problems persist, try clearing the .cache folder with gatsby clean, then restart your development server, which often resolves schema conflicts.