Error: RelayParser: Encountered duplicate defintitions for one or more documents #11688

ChildishhAlbino · 2019-02-11T08:20:22Z

Description

Building a blog / portfolio with GatsbyJS and I'm struggling with this issue. I had the website working for the most part but all of a sudden it's stopped working. Really not sure why. The error doesn't make much sense to me. Hoping someone cold help me work out why.

Steps to reproduce

https://github.com/ChildishhAlbino/childishhalbino.github.io/tree/problem-fixing

Above is a git repo with the project as I last left it.

run NPM install for node packages
Run gatsby develop.
Visit localhost/8000

An error screen should appear with the above error.

Expected result

Page should load without errors.
There should be 3 blog posts with the content from the /posts/ markdown files.
The 'about' tab should display 3 'cards' each with information from the /bio/ markdown files.
The blurb should load with information from the 'blurb.md' file.

There will be warnings. There are some imports that aren't being used but aside from that everything should be fine.

Actual result

Page will not load -> returns above error.
Unsure how else to describe the issue.

Environment

Run npx gatsby info --clipboard in your project directory and paste the output here.

System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Binaries:
npm: 6.4.1 - D:\Software Development\Languages, Frameworks,
etc\nodeJs\npm.CMD
Languages:
Python: 3.7.0 - C:\Users\conno\AppData\Local\Programs\Python\Python37-32\python.EXE
Browsers:
Edge: 42.17134.1.0
npmPackages:
gatsby: ^2.0.118 => 2.0.118
gatsby-image: ^2.0.19 => 2.0.29
gatsby-plugin-buildtime-timezone: ^1.0.3 => 1.0.3
gatsby-plugin-manifest: ^2.0.7 => 2.0.17
gatsby-plugin-offline: ^2.0.23 => 2.0.23
gatsby-plugin-react-helmet: ^3.0.1 => 3.0.6
gatsby-plugin-sass: ^2.0.2 => 2.0.10
gatsby-plugin-sharp: ^2.0.11 => 2.0.20
gatsby-source-filesystem: ^2.0.6 => 2.0.20
gatsby-transformer-remark: ^2.2.4 => 2.2.4
gatsby-transformer-sharp: ^2.1.7 => 2.1.13

error The system cannot find the path specified.

Error: The system cannot find the path specified.

envinfo.js:1 Function.e.exports.sync
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:4970
envinfo.js:1 Object.copySync
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:6694 8
envinfo.js:1 Object.t.writeSync.e [as writeSync]
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:4877 7
envinfo.js:1
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:4693 4
envinfo.js:1 Promise.all.then.e
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:4694 9
util.js:16 tryCatcher
[childishhalbino.github.io]/[bluebird]/js/release/util.js:16 :23
promise.js:512 Promise._settlePromiseFromHandler
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :512:31
promise.js:569 Promise._settlePromise
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :569:18
promise.js:614 Promise._settlePromise0
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :614:10
promise.js:694 Promise._settlePromises
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :694:18
promise.js:638 Promise._fulfill
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :638:18
promise_array.js:126 PromiseArray._resolve
[childishhalbino.github.io]/[bluebird]/js/release/promise_ar ray.js:126:19
promise_array.js:144 PromiseArray._promiseFulfilled
[childishhalbino.github.io]/[bluebird]/js/release/promise_ar ray.js:144:14
promise.js:574 Promise._settlePromise
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :574:26
promise.js:614 Promise._settlePromise0
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :614:10
promise.js:694 Promise._settlePromises
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :694:18

error UNHANDLED REJECTION

Error: The system cannot find the path specified.

envinfo.js:1 Function.e.exports.sync
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:4970
envinfo.js:1 Object.copySync
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:6694 8
envinfo.js:1 Object.t.writeSync.e [as writeSync]
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:4877 7
envinfo.js:1
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:4693 4
envinfo.js:1 Promise.all.then.e
[childishhalbino.github.io]/[envinfo]/dist/envinfo.js:1:4694 9
util.js:16 tryCatcher
[childishhalbino.github.io]/[bluebird]/js/release/util.js:16 :23
promise.js:512 Promise._settlePromiseFromHandler
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :512:31
promise.js:569 Promise._settlePromise
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :569:18
promise.js:614 Promise._settlePromise0
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :614:10
promise.js:694 Promise._settlePromises
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :694:18
promise.js:638 Promise._fulfill
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :638:18
promise_array.js:126 PromiseArray._resolve
[childishhalbino.github.io]/[bluebird]/js/release/promise_ar ray.js:126:19
promise_array.js:144 PromiseArray._promiseFulfilled
[childishhalbino.github.io]/[bluebird]/js/release/promise_ar ray.js:144:14
promise.js:574 Promise._settlePromise
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :574:26
promise.js:614 Promise._settlePromise0
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :614:10
promise.js:694 Promise._settlePromises
[childishhalbino.github.io]/[bluebird]/js/release/promise.js :694:18

The text was updated successfully, but these errors were encountered:

pieh · 2019-02-11T12:57:07Z

This is defenitely a bug in gatsby.

For now you can workaround this by changing line in https://github.com/ChildishhAlbino/childishhalbino.github.io/blob/problem-fixing/gatsby-node.js#L34
to:

component: path.resolve(`./src/components/Blog/BlogPostTemplate/blogPostTemplate.js`),

(I adjusted file/directory names casing to match one that exists in repository). It will get you pass that graphql error, but there will be some additional fixes needed elsewhere too because I hit:

error Building static HTML failed for path "/GatsbyJS and Web development/"

See our docs page on debugging HTML builds for help https://gatsby.app/debug-html

  11 |                  <div className="blurb">
  12 |                          <Image fluid={data.image.childImageSharp.fluid} />
> 13 |                          <Markdown source={data.blurb.childMarkdownRemark.rawMarkdownBody} />
     |                                                                           ^
  14 |                  </div>
  15 |          )}
  16 |  />


  WebpackError: TypeError: Cannot read property 'rawMarkdownBody' of null

But this is not really related to issue itself.

I will start working on fix to handle casing differences and to not throw this confusing error message.

ChildishhAlbino · 2019-02-11T13:19:02Z

Thanks for working that out for me! I actually didn't think it was a bug in Gatsby but whaddya know? ]

Quickly worked out those errors and the sites working again!

Thanks heaps :D

Have a nice day, good luck fixing the bug!

imshuffling · 2019-02-13T09:58:52Z

i think I'm having a similar issue, any update on a fix for this?

pieh · 2019-02-13T11:39:57Z

@imshuffling hopefully I'll open PR today. Just to confirm if your issue have similar root problem - are you on Mac? Because it seems that on Linux and Windows when you use wrong casing for component argument in createPage we will throw error saying that file can't be found.

imshuffling · 2019-02-13T11:43:00Z

@pieh Yeah I'm on a mac, i've logged a issue here - it may be related #11732

pieh · 2019-02-13T13:14:25Z

Oh, this seems different. Error from this is:
Error: RelayParser: Encountered duplicate defintitions for one or more documents

AlexanderProd · 2019-02-16T09:34:00Z

I'm encountering the same bug as well when I create a new gatsby project using this starter and run gatsby develop.

My error message:

GraphQL Error There was an error while compiling your site's GraphQL queries.
  Error: RelayParser: Encountered duplicate defintitions for one or more documents: each document must have a unique name. Duplicated documents:
- usersAlexanderhoerlSitesBiobalanceSrcTemplatesProductPageIndexJs721922104

I'm also on mac.

System:
  OS: macOS 10.14.3
  CPU: (8) x64 Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz
  Shell: 3.2.57 - /bin/bash
Binaries:
  Node: 11.7.0 - /usr/local/bin/node
  Yarn: 1.13.0 - /usr/local/bin/yarn
  npm: 6.5.0 - /usr/local/bin/npm
Languages:
  Python: 2.7.10 - /usr/bin/python
Browsers:
  Chrome: 72.0.3626.109
  Safari: 12.0.3
npmPackages:
  gatsby: ^2.0.111 => 2.0.111 
  gatsby-image: ^2.0.20 => 2.0.25 
  gatsby-plugin-google-analytics: ^2.0.13 => 2.0.13 
  gatsby-plugin-layout: ^1.0.11 => 1.0.11 
  gatsby-plugin-manifest: ^2.0.9 => 2.0.12 
  gatsby-plugin-offline: ^2.0.16 => 2.0.20 
  gatsby-plugin-react-helmet: ^3.0.6 => 3.0.6 
  gatsby-plugin-sharp: ^2.0.14 => 2.0.16 
  gatsby-source-filesystem: ^2.0.8 => 2.0.12 
  gatsby-source-shopify2: ^2.0.7 => 2.0.7 
  gatsby-transformer-sharp: ^2.1.8 => 2.1.9

pieh · 2019-02-16T12:55:55Z

@AlexanderProd From quick look it seems like same issue. This is because
file path casing in https://github.com/AlexanderProd/gatsby-shopify-starter/blob/cff5d01029e514cf9ac8ac70987d01cd03a16f82/gatsby-node.js#L19
doesn't match casing exactly:

in gatsby-node: component: path.resolve(`./src/templates/ProductPage/index.js`),
in filesystem:                             src/templates/productPage/index.js
                                                         ^ one `p` is uppercase other is lower case

so as a workaround, adjusting path in gatsby-node should fix this.

AlexanderProd · 2019-02-18T11:10:53Z

@AlexanderProd From quick look it seems like same issue. This is because
file path casing in https://github.com/AlexanderProd/gatsby-shopify-starter/blob/cff5d01029e514cf9ac8ac70987d01cd03a16f82/gatsby-node.js#L19
doesn't match casing exactly:
in gatsby-node: component: path.resolve(`./src/templates/ProductPage/index.js`),
in filesystem:                             src/templates/productPage/index.js
                                                         ^ one `p` is uppercase other is lower case
so as a workaround, adjusting path in gatsby-node should fix this.

I've noticed when I change it to a small p building and developing works on Ubuntu machines but not on macOS, what makes it pretty difficult to develop on a mac and build on a linux server.

ZolderonGitHub · 2019-06-17T17:48:47Z

i have same problem

mrcongliu · 2019-07-15T01:53:52Z

I met the same error.
The problem is because I was using Hyper terminal in windows.
Solution is using the default terminal in windows.

philkrause · 2019-07-24T22:49:32Z

I met the same error.
The problem is because I was using Hyper terminal in windows.
Solution is using the default terminal in windows.

This solved it for me. Thanks. I did not have this issue on mac.

john20xdoe · 2019-08-04T10:37:54Z

Additional info if anyone else stumble on this issue on Windows:

The gatsby npm run script is case-sensitive not only with the src file names, but including the entire path name:

I store all my projects in a folder in D: named Dev, (D:\Dev)
The "duplicate definitions" error is picking on the entire path (im running in WSL Vscode):
filesystem: /d/Dev/longreponame/gatsby-project/component-name-something
is apparently different from what it is generating:
page: /d/dev/longreponame/gatsby-project/component-name-something

I had to rename the Dev folder to lowercase just to fix it.

patrick-wc · 2019-08-16T08:36:29Z

Gatsby should really add a warning to any Windows users about having capital letters in their dir names. This must stump quite a few users.

drillprop · 2019-08-22T11:50:48Z

I met the same error.
The problem is because I was using Hyper terminal in windows.
Solution is using the default terminal in windows.

works for me too, thank you!

cleophasmogeni · 2019-08-25T21:27:06Z

This error can be quite vague for starters but it is actually a warning due to the case sensitive nature of gatsby run scripts. For example: avoid this Myblog in you file path. You can use myblog or even myBlog

djD-REK · 2019-08-31T16:33:29Z

Gatsby should really add a warning to any Windows users about having capital letters in their dir names. This must stump quite a few users.

Thanks @patrick-wc ! It did stump me!

mickm77 · 2019-09-03T14:02:25Z

On Windows 10 using git bash, i was getting these errors/warnings because I had typed
cd /c/dev/git/projectname
code .

I quit code, and did
cd /C/Dev/Git/projectname
code .

And it all just worked...

lowtolerance · 2019-10-10T16:01:15Z

This started happening to me, seemingly out of nowhere. Exiting out of the command line and reentering seemed to do the trick

8ctopotamus · 2019-10-11T20:54:47Z

This is still happening using Git Bash in VSCode terminal on Windows.

Git Bash by itself works fine.

patrik-u · 2019-10-31T10:41:14Z

On Windows 10 using git bash, i was getting these errors/warnings because I had typed
cd /c/dev/git/projectname
code .

I quit code, and did
cd /C/Dev/Git/projectname
code .

And it all just worked...

Fixed it for me as well. Used Windows PowerShell and worked when I typed cd FolderName with correct casing.

benflinn · 2019-11-17T16:10:12Z

wow i just randomly started having the same error. played around with different content folders for like half an hour before I realized that definitely wasn't it. after renaming my project folder it's working 100% now instantly.

8ctopotamus · 2019-11-22T14:00:24Z

I have found that explicitly typing out cd ~/path/to/project avoids this issue (Using Gitbash in VSCode).

Coffeegerm · 2020-01-15T03:23:10Z

This is still occurring when I run gatsby develop within a PowerShell prompt on Windows, but not when using the Command Prompt

assainov · 2020-03-11T12:41:36Z

For me the error was introduced when I duplicated a src/template/template.js. I moved the file to src/fonts/ folder to eliminate this variant, but gatsby found it even there. Moving the file out of src folder resolved the issue. I think it has to do with a GraphQL queries being similar in different templates.

KishokanthJeganathan · 2020-06-23T16:41:42Z

I had this same issue with when I was having the below code in 2 pages

export const query = graphql`
	query contentFulAddBlogPost($slug: String, $locale: String) {
		contentfulAddBlogPost(path: { eq: $slug }, node_locale: { eq: $locale }) {
			path
			node_locale
		}
	}
`;

to avoid this I changed contentFulAddBlogPost to allContentFulAddBlogPost in one of the components as below

export const query = graphql`
	query allContentFulAddBlogPost($slug: String, $locale: String) {
		contentfulAddBlogPost(path: { eq: $slug }, node_locale: { eq: $locale }) {
			path
			node_locale
		}
	}
`;

worked like a charm. hope it helps you guys in the future :)

pieh added type: bug An issue or pull request relating to a bug in Gatsby status: confirmed Issue with steps to reproduce the bug that’s been verified by at least one reviewer. labels Feb 11, 2019

AlexanderProd mentioned this issue Feb 18, 2019

RelayParser Error AlexanderProd/gatsby-shopify-starter#1

Closed

pieh mentioned this issue Feb 22, 2019

fix(gatsby): normalize component path casing #12005

Merged

sidharthachatterjee closed this as completed in #12005 Feb 25, 2019

shijingl mentioned this issue Apr 25, 2019

Bug in Gatsby? bchiang7/v4#17

Closed

rgiese mentioned this issue Sep 22, 2019

Error: RelayParser: Encountered duplicate defintitions for one or more documents #17811

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: RelayParser: Encountered duplicate defintitions for one or more documents #11688

Error: RelayParser: Encountered duplicate defintitions for one or more documents #11688

ChildishhAlbino commented Feb 11, 2019

pieh commented Feb 11, 2019 •

edited

Loading

ChildishhAlbino commented Feb 11, 2019

imshuffling commented Feb 13, 2019

pieh commented Feb 13, 2019

imshuffling commented Feb 13, 2019

pieh commented Feb 13, 2019

AlexanderProd commented Feb 16, 2019 •

edited

Loading

pieh commented Feb 16, 2019

AlexanderProd commented Feb 18, 2019

ZolderonGitHub commented Jun 17, 2019

mrcongliu commented Jul 15, 2019

philkrause commented Jul 24, 2019

john20xdoe commented Aug 4, 2019 •

edited

Loading

patrick-wc commented Aug 16, 2019

drillprop commented Aug 22, 2019

cleophasmogeni commented Aug 25, 2019

djD-REK commented Aug 31, 2019

mickm77 commented Sep 3, 2019

lowtolerance commented Oct 10, 2019 •

edited

Loading

8ctopotamus commented Oct 11, 2019 •

edited

Loading

patrik-u commented Oct 31, 2019

benflinn commented Nov 17, 2019

8ctopotamus commented Nov 22, 2019

Coffeegerm commented Jan 15, 2020

assainov commented Mar 11, 2020

KishokanthJeganathan commented Jun 23, 2020 •

edited

Loading

Error: RelayParser: Encountered duplicate defintitions for one or more documents #11688

Error: RelayParser: Encountered duplicate defintitions for one or more documents #11688

Comments

ChildishhAlbino commented Feb 11, 2019

Description

Steps to reproduce

Expected result

Actual result

Environment

pieh commented Feb 11, 2019 • edited Loading

ChildishhAlbino commented Feb 11, 2019

imshuffling commented Feb 13, 2019

pieh commented Feb 13, 2019

imshuffling commented Feb 13, 2019

pieh commented Feb 13, 2019

AlexanderProd commented Feb 16, 2019 • edited Loading

pieh commented Feb 16, 2019

AlexanderProd commented Feb 18, 2019

ZolderonGitHub commented Jun 17, 2019

mrcongliu commented Jul 15, 2019

philkrause commented Jul 24, 2019

john20xdoe commented Aug 4, 2019 • edited Loading

patrick-wc commented Aug 16, 2019

drillprop commented Aug 22, 2019

cleophasmogeni commented Aug 25, 2019

djD-REK commented Aug 31, 2019

mickm77 commented Sep 3, 2019

lowtolerance commented Oct 10, 2019 • edited Loading

8ctopotamus commented Oct 11, 2019 • edited Loading

patrik-u commented Oct 31, 2019

benflinn commented Nov 17, 2019

8ctopotamus commented Nov 22, 2019

Coffeegerm commented Jan 15, 2020

assainov commented Mar 11, 2020

KishokanthJeganathan commented Jun 23, 2020 • edited Loading

pieh commented Feb 11, 2019 •

edited

Loading

AlexanderProd commented Feb 16, 2019 •

edited

Loading

john20xdoe commented Aug 4, 2019 •

edited

Loading

lowtolerance commented Oct 10, 2019 •

edited

Loading

8ctopotamus commented Oct 11, 2019 •

edited

Loading

KishokanthJeganathan commented Jun 23, 2020 •

edited

Loading