Gatsby v4 upgrade

[Simply007]

Motivation

Upgrade to be compatible with Gatsby v4

https://v4.gatsbyjs.com/docs/reference/release-notes/migrating-source-plugin-from-v3-to-v4/
https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4

Checklist

• Code follows coding conventions held in this repo
• Automated tests have been added
• Tests are passing
• Docs have been updated (if applicable)
• Temporary settings (e.g. variables used during development and testing) have been reverted to defaults
• Add sample of DSD and SSR to the repo and deploy it to netlify Showcase Gatsby SSR and DSG  #196

How to test

CI is fine

[Simply007]

Version 8.0.0-beta.0 of packages:

• https://www.npmjs.com/package/@kentico/gatsby-source-kontent/v/8.0.0-beta.0
• https://www.npmjs.com/package/@kentico/gatsby-kontent-components/v/8.0.0-beta.0

[Simply007]

TODO:

• - Go through https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/
  • - https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/#replace-nodeinterface-with-interface-inheritance
  • - Define minimal Node version for plugin: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/#minimal-nodejs-version-14150
  • - Replace runQuery: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/#nodemodelrunquery-is-deprecated

[Simply007]

Version 8.0.0-beta.1 of packages:

• https://www.npmjs.com/package/@kentico/gatsby-source-kontent/v/8.0.0-beta.1
• https://www.npmjs.com/package/@kentico/gatsby-kontent-components/v/8.0.0-beta.1

[makma]

Tested on my project, works like a charm. Thanks!

[bwlng]

@Simply007 Tested on our project and it works as expected when upgrading from version 7, but Deferred Static Generation does not work. Adding the defer argument to the createPage action results in the following error.

Gatsby kontent source plugin resulted to error in `createSchemaCustomization` method ENOENT: no such file or directory, open '.cache/query-engine/template.items.schema.gql'

  Error: ENOENT: no such file or directory, open '.cache/query-engine/template.items.schema.gql'

I have a simple reproduction in this repo with reproducible steps in the README.

Would you like me to open a separate issue?

[Simply007]

@Simply007 Tested on our project and it works as expected when upgrading from version 7, but Deferred Static Generation does not work. Adding the defer argument to the createPage action results in the following error.

Gatsby kontent source plugin resulted to error in `createSchemaCustomization` method ENOENT: no such file or directory, open '.cache/query-engine/template.items.schema.gql'

  Error: ENOENT: no such file or directory, open '.cache/query-engine/template.items.schema.gql'

I have a simple reproduction in this repo with reproducible steps in the README.

Would you like me to open a separate issue?

Thanks for testing this out! I was planning to try it myself (#196). And yes please - submit a separate issue. It seems more like a gatsby issue - it might not cache .gql files out of the box (I am using them as a template for schema customization).

[Simply007]

Version 8.0.0-beta.2 of packages:

• https://www.npmjs.com/package/@kentico/gatsby-source-kontent/v/8.0.0-beta.2
• https://www.npmjs.com/package/@kentico/gatsby-kontent-components/v/8.0.0-beta.2

Should fix #197

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[Simply007]

Hello everybody, We are planning to release a final version 8.0.0 in the middle of Feb 2022.

[Simply007]

It is here! 🚀 I am going to release this version as the latest tomorrow (most probably). It is already verified and being used without submitted issues. but one:

• https://discordapp.com/channels/821885171984891914/822034016567689256/940114422268067840

tl;dr; - if you want to use the kontent gatsby source plugin - ideally update to gatsby v 4.6.2 (4.6.1) does not work.

ping @CollierCZ @drewfoster-luminary (thx again for the issue fix) as the thumbs-uppers for the latest comment :)