Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

bump gatsby-source-contentful #392

Merged
merged 1 commit into from
Oct 1, 2019
Merged

Conversation

omonk
Copy link
Contributor

@omonk omonk commented Oct 1, 2019

Description

Recent updates to contentful content type schema caused some issues within gatsby-source-contentful plugin relating to mismatch in typings.

Error looks like this:

  TypeError: entryItemFields[foreignReference.name].push is not a function

  - normalize.js:390 foreignReferences.forEach.foreignReference
    [yld.io]/[gatsby-source-contentful]/normalize.js:390:52

  - Array.forEach

  - normalize.js:365 entries.map.entryItem
    [yld.io]/[gatsby-source-contentful]/normalize.js:365:27

  - Array.map

  - normalize.js:296 locales.forEach.locale
    [yld.io]/[gatsby-source-contentful]/normalize.js:296:32

  - Array.forEach

  - normalize.js:271 Object.exports.createContentTypeNodes
    [yld.io]/[gatsby-source-contentful]/normalize.js:271:11

  - gatsby-node.js:169 contentTypeItems.forEach
    [yld.io]/[gatsby-source-contentful]/gatsby-node.js:169:15

  - Array.forEach

  - gatsby-node.js:168 Object.exports.sourceNodes
    [yld.io]/[gatsby-source-contentful]/gatsby-node.js:168:20

  - next_tick.js:68 process._tickCallback
    internal/process/next_tick.js:68:7

It has been discussed some time ago and reportedly fixed in an update here: gatsbyjs/gatsby#3064

This update has fixed the build from breaking but now gives us some warnings instead, I've reached out to gatsby team to ask for some advice on this: gatsbyjs/gatsby#3064 (comment)

@omonk omonk merged commit b2a4a12 into master Oct 1, 2019
@omonk omonk deleted the FIX-update-gatsby-source-contentful branch October 7, 2019 04:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants