broken reef
Hello, I've setup a project to use gatsbyjs v4, directus, postcss/tailwind each system works individually when combined you get the attached error message randomly, also if you do get a successful build the results of your graphql will often have null values that previously worked. I have a feeling there is some sort of sequencing issue with the directus gatsbyjs plugin
smoky glen
Are you on latest gatsby and latest plug-in? So far when I’ve seen any random null values it’s been due to versions.
broken reef
Yes, but it appears to be more related to when I installed postcss and tailwind, I was able to use react components and all my issues clear up
I am using v4, the directus plugin doesn't work at all with v5
I noticed that if a postcss/tailwind + directus installation if it doesn't panic has random null values
Also I discovered the issue appears again if I used the sass plugin, I think there is some race condition with their parallel builds
I had noticed that the directus plugin is using v9 of the directus sdk, not v10
The null values are related to images, so probably something is going on with image sharp
smoky glen
Yeah in terms of v5, we need to do some work for it, not sure why postcss or sass would cause issues though.
broken reef
i've put my project up at https://github.com/WestForge/avalon-myth-of-albion/tree/crazy-experiment and stripped it back to the essentials, i've upgraded to the latest 9.14.4 and it causes Panicking because nodes appear to be being changed every time we run queries. This would cause the site to recompile infinitely. almost every time, however if i downgrade to v9.14.1 the issue goes away
smoky glen
I’ll do some testing with postcss / tailwind but not seeing any of that outside of using postcss. .5 just updated the SDK, and we’ll be doing a v10 release for gatsby 5 as some of the internal handling changed things but no release date for it yet.
broken reef
i've removed tailwind now and downgraded to v9.14.1 and the problem has gone away
smoky glen
Yeah it’s not a behaviour I’ve seen without postcss and been doing a lot of Gatsby testing /dev the last couple weeks.
broken reef
i think i had something cached, which was giving me some weird results, looking back i think it was all 9.14.4 related, i noticed a .5 is out upgrading the SDK
smoky glen
Yes 5 was released this week and that .cache folder can be tricky. I always nuke it before any build
broken reef
i think something got stuck on the directus plugin on v9.14.4 and kept giving me problems, i've deleted almost everything and started again
.4 screws me over, .1 works just fine, i should compare the differences
smoky glen
Main differences were some sharp support that was added in .3, .4 had a fix related to if directus was in a folder or not