Andreas Odysseos

I've been getting the same since yesterday and is been blocking a project from going live! Nightmare @joeweale !!! Any thought will be great! Thanks

Potentially falling back to "gatsby-source-graphql-universal": "3.3.0" could fix the issue. I've tried it on a new project and it work. I'm now applying it on my project. Fingers crossed!

@AndrejGajdos I have: - "gatsby": "^2.21.37", - "gatsby-source-prismic-graphql": "^3.6.2", - "gatsby-source-graphql-universal": "3.3.0" and running node v10.13.0 If that helps

So I managed to work around it for now by using the following in my package.json - "gatsby": "^2.21.37", - "gatsby-source-graphql-universal": "3.3.0", - "gatsby-source-prismic-graphql": "3.4.0-beta.1" It seems that gatsby-source-prismic-graphql installs...

I had the same issue. Building the project for production is causing all JS events like onClick to stop working. I've manage to work around it my using version: 3.4.0-beta.1...