Build issues with Gatsby on Sanity blog starter project

Hey all! Has anyone had any build issues when trying to run a gatsby build on the Sanity blog starter project? I am getting this…

Thanks for the heads up, User! There should be a line at the top of that file:
It should also check for empty

publishedAt

fields in the GraphQL query. I’ll check if I can reproduce the issue 👍

Thanks User. Yes I see it. I do have a draft that’s not been published and without a date. That’s been the only change on the project so far..

The graphql does filter them…

I had the same kind of problem with date in Gatsby before: that was a matter of date format. Here I see

YYYY/MM

and Gatsby only accept

YYYY-MM

or may be complete

YYYY-MM-DD

. I am not sure though.

Here is a data dump of the data it’s looping through.

Hi again User, I just tried to replicate the issue by starting from scratch at https://www.sanity.io/create with the Gatsby blog template. However, it successfully runs

gatsby develop

and

gatsby build && gatsby serve

in /web, as well as

npm run build

in root. So it looks like we need to dive in deeper to figure out what the issue is.
You created your project via
sanity.io/create , correct? And you get the error when running your build locally? Have you tried re-creating the blog from scratch?

That’s correct yeah. Haven’t tried re-creating it from scratch… i’ll give it a try tomorrow and see how I get on and let you know. Thanks for looking into it User 👍

Ok, so I can confirm that the problem was upgrading the projects dependencies. (forgot that I did that, sorry). So it appears to be a problem with 1 or more of the following deps. (Not including latest gatsby as it still builds on the below version)

Might be worth trying to replicate with that and see if you have the same build problem. I’m unable to go through each dependancie at the moment to see which ones are causing the problems, but if you’d like me to when i’m able, please let me know 🙂

There does seem to be a particular issue around using the latest date-fns, for which gave a possible work around. with the below

Hi again User, thanks for confirming and for sharing all these extra details 👍 Looks like we have to do some maintenance to bring the template up to the latest version of

date-fns

without breaking it 🙂 Hope you can move forward for now, but I’ll ping you when we release an update.

Thanks User, that would be great. Thanks for your help on this 👍