Hey everyone! I’m having trouble with my Gatsby site after I installed and configured the gatsby-source-figma plugin. Every time I try to start the development server, I get this annoying error that stops everything from working.
The error message says something like “Missing onError handler for invocation ‘building-schema’” and then mentions “Type with name ‘FigmaELLIPSE’ does not exists”. It seems like there’s some kind of schema building problem happening.
I followed the setup instructions for the plugin but I must be missing something. Has anyone else run into this issue before? I really need to get this working so I can pull design data from Figma into my Gatsby project. Any help would be really appreciated!
I encountered this exact same error last month when working on a client project. The issue stems from the gatsby-source-figma plugin trying to create GraphQL types for Figma nodes that don’t match the expected schema structure. The ‘FigmaELLIPSE’ type error usually occurs when the plugin encounters specific node types in your Figma file that it cannot properly parse. What fixed it for me was clearing the Gatsby cache completely and then checking my Figma file structure. Make sure your Figma access token has the correct permissions and that the file ID in your gatsby-config.js is accurate. Also verify that your Figma file doesn’t contain any corrupted or unusual elements that might be causing the schema generation to fail. Try running gatsby clean followed by gatsby develop to see if that resolves the type generation issue.
This error drove me crazy for days until I figured out the root cause. The problem isn’t actually with your configuration but with how the plugin handles certain Figma node types during the GraphQL schema generation phase. When Figma files contain ellipse objects with specific properties or nested components, the gatsby-source-figma plugin sometimes fails to create the proper type definitions. I solved this by temporarily removing or simplifying complex ellipse elements in my Figma file, running the build successfully to establish the base schema, then gradually adding back the complex elements. Another workaround that worked was updating to the latest version of the plugin and ensuring my Node.js version was compatible. The plugin documentation mentions some known issues with certain Figma object types, so checking their GitHub issues page might reveal if this is a known bug with your specific plugin version.
sounds like a plugin versioning issue tbh. had similiar problems with figma graphql types not generating correctly. try downgrading gatsby-source-figma to an earlier version - the newer ones sometimes break with certain figma elements. also check if your figma file has any hidden layers or components that might be cuasing the schema parser to choke.