Gatsby: Validation errors with [email protected]

Created on 15 Apr 2018  Â·  7Comments  Â·  Source: gatsbyjs/gatsby

Description

After upgrading to [email protected], I'm seeing this validation issue:

The new node didn't pass validation
ValidationError: child "internal" fails because ["description" is not allowed]

Steps to reproduce

npm install [email protected] [email protected]

In gatsby-config.js:

module.exports = {
  plugins: [
    {
      resolve: 'gatsby-source-filesystem',
      options: {
        name: 'src',
        path: `${__dirname}/src/`
      }
    }
  ]
};

Run npx gatsby develop with a few files in the src directory.

Expected result

No validation errors.

Actual result

The new node didn't pass validation
ValidationError: child "internal" fails because ["description" is not allowed]
{ id: '/path/to/gatsby-site/src/pages/index.js absPath of file',
  children: [],
  parent: '___SOURCE___',
  internal: 
   { contentDigest: '19d579cf1c21a7306f3ec59289ee8382',
     mediaType: 'application/javascript',
     type: 'File',
     description: 'File "src/pages/index.js"',
     owner: 'gatsby-source-filesystem' },
  sourceInstanceName: 'src',
  absolutePath: '/path/to/gatsby-site/src/pages/index.js',
  relativePath: 'pages/index.js',
  extension: 'js',
  // etc

Downgrading to [email protected] resolves the issue.

Environment

  • Gatsby version: 1.9.249
  • gatsby-cli version: 1.9.249
  • Node.js version: 8.9.1
  • Operating System: macOS 10.13.4

Most helpful comment

Confirmed that upgrading to [email protected] fixes the issue.

All 7 comments

I see the validation change in https://github.com/gatsbyjs/gatsby/pull/3905/files#diff-bd517ec758aa05f3e6e1c34b15f65394R60

Looks like [email protected] depends on [email protected].

Confirmed that upgrading to [email protected] fixes the issue.

I was getting the same error and have been trying to fix it for 2 hours! Thank you so much for posting this! it fixed it for me as well. I was getting super frustrated...

I can confirm it fixed it for me as well.

I'll close this issue as problem was resolved. If anyone will have same error, solution is presented here.

We should bump the peerDependency for gatsby to when we added description
support

On Sun, Apr 15, 2018, 10:56 AM Michal Piechowiak notifications@github.com
wrote:

Closed #4985 https://github.com/gatsbyjs/gatsby/issues/4985.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby/issues/4985#event-1575043027, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEVh0hPrg_kmGTATfz71EqbpCiAV-6Mks5to4nXgaJpZM4TVUXn
.

Worked for me. Just upgraded gatsby to no more errors.

As a reference and no brainer: npm update gatsby fixed it for me

Was this page helpful?
0 / 5 - 0 ratings

Related issues

andykais picture andykais  Â·  3Comments

magicly picture magicly  Â·  3Comments

hobochild picture hobochild  Â·  3Comments

ferMartz picture ferMartz  Â·  3Comments

Oppenheimer1 picture Oppenheimer1  Â·  3Comments