Cannot find module './third-party/gatsby-node'

joeweale commented 4 years ago

Getting an error on build;

Error in "C:...\node_modules\gatsby-source-prismic-graphql\gatsby-node.js": Cannot find module './third-party/gatsby-node'

Any ideas?

Thanks

Joe

aodysseos commented 4 years ago

I've been getting the same since yesterday and is been blocking a project from going live!

Nightmare @joeweale !!!

Any thought will be great!

Thanks

AndrejGajdos commented 4 years ago

I have the same issue

aodysseos commented 4 years ago

Potentially falling back to "gatsby-source-graphql-universal": "3.3.0" could fix the issue. I've tried it on a new project and it work. I'm now applying it on my project. Fingers crossed!

AndrejGajdos commented 4 years ago

@aodysseos I tried gatsby-source-prismic-graphql 3.6.2, 3.5.0, 3.3.0 and I still get the same error.

edit:// I am not using gatsby-source-graphql-universal, only gatsby-source-prismic-graphql

aodysseos commented 4 years ago

@AndrejGajdos I have:

"gatsby": "^2.21.37",
"gatsby-source-prismic-graphql": "^3.6.2",
"gatsby-source-graphql-universal": "3.3.0"

and running node v10.13.0

If that helps

AndrejGajdos commented 4 years ago

@aodysseos thanks I checked my package.json and I don't use gatsby-source-graphql-universal. I use only gatsby-source-prismic-graphql. I tried gatsby-source-prismic-graphql three different versions 3.6.2, 3.5.0, 3.3.0 and it didn't help.

I tried to add "gatsby-source-graphql-universal": "3.3.0" dependency and it didn't solve the issue.

Do you mean changing gatsby-source-graphql-universal inside gatsby-source-prismic-graphql?

NSpehler commented 4 years ago

Same problem here...

jodiedoubleday commented 4 years ago

Yep this seem to have started happening this morning

NSpehler commented 4 years ago

aodysseos commented 4 years ago

So I managed to work around it for now by using the following in my package.json

"gatsby": "^2.21.37",
"gatsby-source-graphql-universal": "3.3.0",
"gatsby-source-prismic-graphql": "3.4.0-beta.1"

It seems that gatsby-source-prismic-graphql installs the latest version of gatsby-source-graphql-universal as a dependancy which has the issue. By forcing a specific version and using a previous version of gatsby-source-prismic-graphql I got around the problem for now and got my project to build.

NOTE: gatsby-source-graphql-universal was updated 20hrs ago so I'm guessing that caused it.

Hope that helps

NSpehler commented 4 years ago

@aodysseos The exact same configuration didn't fix it for me.

riccoski commented 4 years ago

I've got it working by installing: "gatsby-source-graphql-universal": "3.3.0", and removing "gatsby-source-graphql-universal" from node_modules/gatsby-source-prismic/node_modules.

It still installs 3.4.0 in there

zpthree commented 4 years ago

I got it working by deleting node_modules, adding a yarn dependency resolution to my package.json, and reinstalling with yarn. Hopefully this issue gets fixed soon.

"resolutions": { "gatsby-source-graphql-universal": "3.3.0" },

codebravotech commented 4 years ago

Same issue!

Edit: locking the dependency using a resolutions block as per zpthree's suggestion is the correct workaround.

botre commented 4 years ago

Same issue using Windows 10, unfortunately I don't use Yarn so the resolution workaround isn't available to me.

mrseanbaines commented 4 years ago

Filed an issue with Gatsby before finding out this package wasn't maintained by them. Here's my report with a few extra details and an example site:

Description

Following setup instructions from various sources (e.g. here), gatsby-source-prismic-graphql throws the following error:

Error: Cannot find module './third-party/gatsby-node'
Require stack:
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby-source-graphql-universal/gatsby-node.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby-source-prismic-graphql/gatsby-node.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby/dist/bootstrap/resolve-module-exports.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby/dist/bootstrap/load-plugins/validate.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby/dist/bootstrap/load-plugins/load.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby/dist/bootstrap/load-plugins/index.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby/dist/bootstrap/index.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby/dist/commands/develop.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby-cli/lib/create-cli.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby-cli/lib/index.js
- /Users/mrseanbaines/projects/gatsby-prismic-blog/node_modules/gatsby/dist/bin/gatsby.js

Steps to reproduce

npx gatsby new gatsby-prismic-blog
cd gatsby-prismic-blog
yarn add gatsby-source-prismic-graphql prismic-javascript prismic-reactjs
yarn start

Minimal Reproduction: https://github.com/mrseanbaines/gatsby-prismic-blog

Expected result

Start local dev server without error.

Actual result

Error throws when starting local dev server.

Environment

  System:
    OS: macOS 10.15.4
    CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.16.1 - /usr/local/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.13.4 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 83.0.4103.61
    Firefox: 76.0.1
    Safari: 13.1
  npmPackages:
    gatsby: ^2.21.37 => 2.21.37 
    gatsby-image: ^2.4.4 => 2.4.4 
    gatsby-plugin-manifest: ^2.4.5 => 2.4.5 
    gatsby-plugin-offline: ^3.2.3 => 3.2.3 
    gatsby-plugin-react-helmet: ^3.3.1 => 3.3.1 
    gatsby-plugin-sharp: ^2.6.4 => 2.6.4 
    gatsby-source-filesystem: ^2.3.4 => 2.3.4 
    gatsby-source-prismic-graphql: ^3.6.2 => 3.6.2 
    gatsby-transformer-sharp: ^2.5.2 => 2.5.2

miraclemaker commented 4 years ago

I ran into the same issue when updating my packages and solved it by reverting back to the following versions: "gatsby": "^2.20.19", "gatsby-plugin-sharp": "^2.5.4", "gatsby-source-filesystem": "^2.2.2", "gatsby-source-prismic-graphql": "^3.6.2", "gatsby-transformer-sharp": "^2.4.4",

All of these may not be required but I didn't have any more time to spend on it.

benwalio commented 4 years ago

running into the exact same issue here.

gatsby info

  System:
    OS: macOS 10.15.4
    CPU: (8) x64 Intel(R) Core(TM) i7-1060NG7 CPU @ 1.20GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.0.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.5 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Firefox: 76.0.1
    Safari: 13.1
  npmPackages:
    gatsby: ^2.22.12 => 2.22.12
    gatsby-image: ^2.4.4 => 2.4.5
    gatsby-plugin-manifest: ^2.4.5 => 2.4.5
    gatsby-plugin-offline: ^3.2.3 => 3.2.3
    gatsby-plugin-react-helmet: ^3.3.1 => 3.3.1
    gatsby-plugin-sharp: ^2.6.4 => 2.6.4
    gatsby-source-filesystem: ^2.3.4 => 2.3.8
    gatsby-source-prismic-graphql: ^3.6.2 => 3.6.2
    gatsby-transformer-sharp: ^2.5.2 => 2.5.2
  npmGlobalPackages:
    gatsby-cli: 2.12.37

AndrejGajdos commented 4 years ago

@zpthree Thanks for the fix, I didn't know yarn has such a nice feature.

subhashb commented 4 years ago

Just adding more information why this issue cropped up.

I hacked my way through this issue by force-creating the gatsby-node.js in the right folder, and it works for development.

Steps:

Locate gatsby-source-graphql-universal in your node_modules
Create a folder called third-party in the folder
Copy this gatsby-node.js file into the folder

This won't work for production, of course. This is the commit that broke the setup. The reason is that the new third-party folder was not included in packaging.

I just created a new issue on that repo.

RectoVersoDev commented 4 years ago

Same problem here 😥

joshua-isaac commented 4 years ago

I'm getting the same problem, hopefully this issue can get resolved 🙏🏽

olonade43 commented 4 years ago

Reverting is working for me locally but still breaks for me during deploys to production. Anyone else running into that?

TatsumiSuenaga commented 4 years ago

@aodysseos

So I managed to work around it for now by using the following in my package.json

"gatsby": "^2.21.37",

"gatsby-source-graphql-universal": "3.3.0",

"gatsby-source-prismic-graphql": "3.4.0-beta.1"

It seems that gatsby-source-prismic-graphql installs the latest version of gatsby-source-graphql-universal as a dependancy which has the issue. By forcing a specific version and using a previous version of gatsby-source-prismic-graphql I got around the problem for now and got my project to build.

NOTE: gatsby-source-graphql-universal was updated 20hrs ago so I'm guessing that caused it.

Hope that helps

Thanks! This worked for me after I cleared my ./node_modules/

EDIT: Nevermind, build fails in prod/staging

Bram-Zijp commented 4 years ago

This should work fine as quick and dirty temp workaround

mbbillz commented 4 years ago

Same issue...

iamsainikhil commented 4 years ago

Resolutions can be added in NPM similar to Yarn using this package -> https://github.com/rogeriochaves/npm-force-resolutions

Add the below preinstall script in package.json

"scripts": {
"preinstall": "npx npm-force-resolutions"
}

Add the gatsby-source-graphql-universal in resolutions

"resolutions": { 
"gatsby-source-graphql-universal": "3.3.0" 
}

Run the npm install

noblica commented 4 years ago

Yup, same issue here. Hopefully it gets fixed soon.

tynsoltys commented 4 years ago

The one day I find some time to muck around with prismic this happens, of course.

joshua-isaac commented 4 years ago

would i be fine just using gatsby-source-prismic instead of this plugin? Am i losing any major benefits going that route?

iamsainikhil commented 4 years ago

would i be fine just using gatsby-source-prismic instead of this plugin? Am i losing any major benefits going that route?

To be honest, I moved away from this plugin to using gatsby-source-prismic and I am loving it (in terms of GraphQL queries). I don't have much experience using both plugins so I couldn't answer your second question.

Just keep in mind that gatsby-source-prismic have some issues regarding PrismicImageFixedType not found error while doing gatsby-develop in the latest version. So, stick to using v3.0.2 for the stable version. For more info regarding this issue, check here -> https://github.com/angeloashmore/gatsby-source-prismic/issues/238

joshua-isaac commented 4 years ago

would i be fine just using gatsby-source-prismic instead of this plugin? Am i losing any major benefits going that route?

To be honest, I moved away from this plugin to using gatsby-source-prismic and I am loving it (in terms of GraphQL queries). I don't have much experience using both plugins so I couldn't answer your second question.

Just keep in mind that gatsby-source-prismic have some issues regarding PrismicImageFixedType not found error while doing gatsby-develop in the latest version. So, stick to using v3.0.2 for the stable version. For more info regarding this issue, check here -> angeloashmore/gatsby-source-prismic#238

Thanks for this Sai, i will take a look at that plugin then 😀

iamsainikhil commented 4 years ago

@joshua-isaac It might be good to read this article to know the exact differences between both the plugins. It might also help you migrate your project from one plugin to another.

https://user-guides.prismic.io/en/articles/3647135-how-to-migrate-a-project-from-gatsby-source-prismic-to-gatsby-source-prismic-graphql

Bram-Zijp commented 4 years ago

@joshua-isaac One of the downsides is you need to implement a preview mechanism yourself if you want to use such thing. Recently the preview implementation of this the prismic-graphql plugin must have had some love because it's working like a charm for me since recently.

rowin1125 commented 4 years ago

Anyone knows the current progress of resolving this issue ?

miraclemaker commented 4 years ago

@joshua-isaac One of the downsides is you need to implement a preview mechanism yourself if you want to use such thing. Recently the preview implementation of this the prismic-graphql plugin must have had some love because it's working like a charm for me since recently.

@Bram-Zijp any tips on getting previews working? I've been having some problems detailed here.

rowin1125 commented 4 years ago

@Bram-Zijp

This should work fine as quick and dirty temp workaround

Only issue im facing with this that it isn't fetching the staticQueries and doesnt return any network errors, console errors or a error while doing the yarn develop command:

morszczuk commented 4 years ago

@rowin1125 I am experiencing the same issue. The quick fixes proposed above fix the third-party folder issue and allows the gatsby site to run in development mode. Unfortunately, at the same time components which use StaticQuery stopped working and the production build fails as well.

By not working, I mean:

gatsby develop successfully starts the website, but components which use StaticQuery does not render correctly. Instead, the text "Loading (StaticQuery)" is presented (exactly in the same way as on @rowin1125 screenshots).
gatsby build - build fails during the "Building production Javascript and CSS bundles" step.

Errors, which make the build fail, come only from the StaticQuery files. It is worth noting, that the queries passed to StaticQuery run correctly - their results are added to the ../../public/static/d/ folder in the earlier step of the build. Then, for some reason, StaticQuery components are not rendered into the ../../public/static/d/, causing the build to fail.

Does anyone have an idea, why this quick fix (reverting gatsby-source-graphql-universal to version 3.3.0) causes the StaticQuery to fail?

This is the log of the failed build:

failed Building production JavaScript and CSS bundles - 28.094s

ERROR #98124  WEBPACK
Generating JavaScript bundles failed
Can't resolve '../../public/static/d/1207704026.json' in '... src/components'

If you're trying to use a package make sure that '../../public/static/d/1207704026.json' is installed. If you're trying to use a local file make sure that the path is correct.

File: src/components/seo.js

ERROR #98124  WEBPACK
Generating JavaScript bundles failed
Can't resolve '../../public/static/d/3588910319.json' in '.../src/components'

If you're trying to use a package make sure that '../../public/static/d/3588910319.json' is installed. If you're trying to use a local file make sure that the path is correct.

File: src/components/footer.js
-

This is the overall structure of the src/components/footer.js:

import React from "react"
import { Link, StaticQuery, graphql } from 'gatsby';
import { withPreview } from 'gatsby-source-prismic-graphql';
// ...
const footerQuery = graphql`
  query FooterQuery { ... }
`

const renderFooter = ({ data }) => { return (<footer>...</footer>) }

const Footer = () => {
  return (
    <StaticQuery
      query={footerQuery}
      render={withPreview((data) => { return renderFooter({ data: data }) }, footerQuery)}
    />
  );
}

steoneill commented 4 years ago

I'm seeing this, also!

AndrejGajdos commented 4 years ago

@morszczuk I have the same issue

aodysseos commented 4 years ago

@rowin1125 I am experiencing the same issue. The quick fixes proposed above fix the third-party folder issue and allows the gatsby site to run in development mode. Unfortunately, at the same time components which use StaticQuery stopped working and the production build fails as well.

By not working, I mean:

gatsby develop successfully starts the website, but components which use StaticQuery does not render correctly. Instead, the text "Loading (StaticQuery)" is presented (exactly in the same way as on @rowin1125 screenshots).

gatsby build - build fails during the "Building production Javascript and CSS bundles" step.

Errors, which make the build fail, come only from the StaticQuery files. It is worth noting, that the queries passed to StaticQuery run correctly - their results are added to the ../../public/static/d/ folder in the earlier step of the build. Then, for some reason, StaticQuery components are not rendered into the ../../public/static/d/, causing the build to fail.

Does anyone have an idea, why this quick fix (reverting gatsby-source-graphql-universal to version 3.3.0) causes the StaticQuery to fail?

This is the log of the failed build:
failed Building production JavaScript and CSS bundles - 28.094s

ERROR #98124  WEBPACK
Generating JavaScript bundles failed
Can't resolve '../../public/static/d/1207704026.json' in '... src/components'

If you're trying to use a package make sure that '../../public/static/d/1207704026.json' is installed. If you're trying to use a local file make sure that the path is correct.

File: src/components/seo.js

ERROR #98124  WEBPACK
Generating JavaScript bundles failed
Can't resolve '../../public/static/d/3588910319.json' in '.../src/components'

If you're trying to use a package make sure that '../../public/static/d/3588910319.json' is installed. If you're trying to use a local file make sure that the path is correct.

File: src/components/footer.js
- 
This is the overall structure of the src/components/footer.js:
import React from "react"
import { Link, StaticQuery, graphql } from 'gatsby';
import { withPreview } from 'gatsby-source-prismic-graphql';
// ...
const footerQuery = graphql`
  query FooterQuery { ... }
`

const renderFooter = ({ data }) => { return (<footer>...</footer>) }

const Footer = () => {
  return (
    <StaticQuery
      query={footerQuery}
      render={withPreview((data) => { return renderFooter({ data: data }) }, footerQuery)}
    />
  );
}

@morszczuk I had the same issue recently and fixed it by using "gatsby": "2.17.10"

AndrejGajdos commented 4 years ago

@aodysseos I am getting this error https://github.com/gatsbyjs/gatsby/issues/23214 with "gatsby": "2.17.10"

aodysseos commented 4 years ago

Hi @AndrejGajdos it is pretty much a battle with dependencies versions!

Here is what I am using:

"gatsby": "2.17.10"
"gatsby-source-graphql-universal": "3.3.0",
"gatsby-source-prismic-graphql": "3.4.0-beta.1"

Node 10.20.1

Make sure to gatsby clean, delete node_modules and package_json.

It's not that this is the only way to fix the issue, it is just what I found that worked for me! Hope it helps.

AndrejGajdos commented 4 years ago

@aodysseos thanks, I tried these versions, but I still get the same erros:

This is my package.json:

"dependencies": {
    "@fortawesome/fontawesome-svg-core": "^1.2.25",
    "@fortawesome/free-brands-svg-icons": "^5.12.0",
    "@fortawesome/free-solid-svg-icons": "^5.11.2",
    "@fortawesome/react-fontawesome": "^0.1.7",
    "@kunukn/react-collapse": "1",
    "@material-ui/core": "^4.9.5",
    "@popperjs/core": "^2.3.3",
    "add": "^2.0.6",
    "axios": "^0.19.0",
    "basic-auth": "^2.0.1",
    "bootstrap": "4.2.1",
    "chart.js": "^2.9.3",
    "d3-node": "^2.2.1",
    "debug": "^4.1.1",
    "font-awesome": "4.7.0",
    "framer-motion": "^1.10.3",
    "gatsby": "2.17.10",
    "gatsby-plugin-canonical-urls": "^2.3.0",
    "gatsby-plugin-dark-mode": "^1.1.0",
    "gatsby-remark-autolink-headers": "^2.3.3",
    "gatsby-remark-embed-video": "^3.0.10",
    "gatsby-source-git": "^1.0.2",
    "gatsby-source-prismic-graphql": "3.4.0-beta.1",
    "gatsby-transformer-remark": "^2.6.53",
    "lodash.get": "^4.4.2",
    "lodash.groupby": "^4.6.0",
    "lodash.pickby": "^4.6.0",
    "lodash.set": "^4.3.2",
    "lodash.update": "^4.10.2",
    "marked": "^0.8.0",
    "moment": "^2.24.0",
    "prismic-reactjs": "^1.3.1",
    "prop-types": "^15.7.2",
    "react-chartjs-2": "^2.8.0",
    "react-collapsible": "^2.6.3",
    "react-d3-components": "^0.9.1",
    "react-d3-library": "^1.1.8",
    "react-headroom": "^3.0.0",
    "react-helmet": "^5.2.0",
    "react-lazyload": "^2.6.5",
    "react-moment": "^0.9.6",
    "react-onclickout": "^2.0.8",
    "react-popper": "^2.2.3",
    "react-popper-tooltip": "^2.11.1",
    "react-responsive": "^8.0.1",
    "react-scroll-to": "^3.0.0-beta.3",
    "react-select": "^3.1.0",
    "react-sidebar": "^3.0.2",
    "react-slick": "^0.25.2",
    "react-svg-donuts": "^1.0.0",
    "react-telegram-embed": "^0.0.10",
    "react-toastify": "^5.4.1",
    "react-twitter-embed": "^3.0.3",
    "react-window": "^1.8.5",
    "reactstrap": "^8.4.1",
    "slick-carousel": "^1.8.1",
    "underscore": "^1.9.1",
    "yarn": "^1.21.1"
  },
  "devDependencies": {
    "@prototype-interactive/eslint-config": "^0.1.1",
    "autoprefixer": "^9.4.4",
    "cross-env": "^5.2.0",
    "dotenv": "^8.2.0",
    "eslint": "^5.12.0",
    "gatsby-plugin-google-analytics": "^2.3.0",
    "gatsby-plugin-postcss": "^2.0.2",
    "gatsby-plugin-postcss-sass": "^1.0.22",
    "gatsby-plugin-react-helmet": "^3.0.5",
    "gatsby-plugin-sass": "^2.0.7",
    "gatsby-source-filesystem": "^2.2.2",
    "gatsby-transformer-json": "^2.1.7",
    "gh-pages": "^2.0.1",
    "husky": "^1.3.1",
    "prettier": "^1.15.3",
    "pretty-quick": "^1.8.0",
    "react": "^16.7.0",
    "react-dom": "^16.7.0",
    "shx": "^0.3.2",
    "svg-sprite-loader": "^4.1.3"
  },
  "resolutions": {
    "gatsby-source-graphql-universal": "3.3.0",
    "graphql": "^14.6.0"
  },

morszczuk commented 4 years ago

@AndrejGajdos I was getting the same error when I downgraded the gatsby version.

Thanks for all of the answers in this thread - I managed to make my website work 🙌 I have to admit, I struggled a little bit to find a correct combination of the versions. At the end, I used the fact that my website was "on production" and I just arbitrary used dependencies and package-lock.json from the last successful build. This is the list (you would probably still need to lock the gatsby-source-graphql-universal to version 3.3.0 through one of the ways mentioned above):

"dependencies": {
    "bootstrap": "4.4.1",
    "classnames": "2.2.6",
    "gatsby": "2.19.7",
    "gatsby-image": "2.2.39",
    "gatsby-plugin-google-analytics": "2.2.5",
    "gatsby-plugin-manifest": "2.3.3",
    "gatsby-plugin-offline": "3.0.32",
    "gatsby-plugin-preload-fonts": "1.1.1",
    "gatsby-plugin-react-helmet": "3.1.21",
    "gatsby-plugin-sharp": "2.5.4",
    "gatsby-source-filesystem": "2.1.46",
    "gatsby-source-prismic-graphql": "3.5.0",
    "gatsby-transformer-sharp": "2.4.4",
    "gatsby-transformer-sqip": "2.2.4",
    "html-react-parser": "0.10.2",
    "prism-react-renderer": "1.0.2",
    "prismic-reactjs": "1.2.0",
    "prop-types": "15.7.2",
    "react": "16.12.0",
    "react-bootstrap": "1.0.0-beta.16",
    "react-dom": "16.12.0",
    "react-helmet": "5.2.1",
    "react-inlinesvg": "1.2.0",
    "react-markdown": "4.3.1",
    "react-router-dom": "5.1.2",
    "reactstrap": "8.4.1"
  },

AndrejGajdos commented 4 years ago

@morszczuk if I use the same versions as you, I still get this error. I think it is because very using different versions of gatsby cli. If you run gatsby -v in command line what version do you get?

morszczuk commented 4 years ago

@AndrejGajdos

Gatsby CLI version: 2.12.40
Gatsby version: 2.19.7

AndrejGajdos commented 4 years ago

@morszczuk Damn, I still get this error and I have the same versions.

jodiedoubleday commented 4 years ago

@AndrejGajdos you're not alone. I have the same issues you are seeing, I'm struggling to resolve them if I find anything I'll let you know.

Bram-Zijp commented 4 years ago

With my solution, everything works as expected for me. Previews work and builds work and it's been running in production for about 20 days without any issues.

Problems with builds with Gatsby can generally be fixed by removing the build, .cache and in some cases the node_moduels too (don't forget to reinstall node_modules).

I am curious if you guys had the previews and all working before updating the version.

I personally don't generate pages dynamically yet. This seems like a variable that might be reason for other people not getting it to work. This is a wild guess without having looked into the updates of this module since it started to break.

I use the method as described in #228 to inject the preview script.

These are my relevant configurations:

    {
      options: {
        omitPrismicScript: true,
        path: '/preview', // (optional preview path. Default: /preview)
        previews: true, // (optional, activated Previews. Default: false)
        repositoryName: 'my-name-here', // (REQUIRED, replace with your own)
      },
      resolve: 'gatsby-source-prismic-graphql',
    },

System:
  OS: Windows 10 10.0.18363
  CPU: (12) x64 Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
Binaries:
  Node: 14.3.0 - C:\Program Files\nodejs\node.EXE
  Yarn: 1.22.4 - ~\AppData\Roaming\npm\yarn.CMD
  npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
Languages:
  Python: 2.7.15 - /c/Users/bramz/.windows-build-tools/python27/python
Browsers:
  Edge: 44.18362.449.0
npmPackages:
  gatsby: ^2.22.17 => 2.22.17 
  gatsby-image: ^2.4.6 => 2.4.6 
  gatsby-plugin-emotion: ^4.3.3 => 4.3.3 
  gatsby-plugin-generate-types: ^0.1.0 => 0.1.0 
  gatsby-plugin-manifest: ^2.4.10 => 2.4.10 
  gatsby-plugin-netlify: ^2.3.4 => 2.3.4 
  gatsby-plugin-netlify-cache: ^1.2.0 => 1.2.0 
  gatsby-plugin-offline: ^3.2.8 => 3.2.8 
  gatsby-plugin-react-helmet: ^3.3.3 => 3.3.3 
  gatsby-plugin-sharp: ^2.6.10 => 2.6.10 
  gatsby-plugin-sitemap: ^2.4.4 => 2.4.4 
  gatsby-plugin-ts-config: ^0.2.2 => 0.2.2 
  gatsby-plugin-typegen: ^2.2.0 => 2.2.0 
  gatsby-plugin-typescript: ^2.4.4 => 2.4.4 
  gatsby-source-filesystem: ^2.3.10 => 2.3.10 
  gatsby-source-prismic-graphql: ^3.6.2 => 3.6.2 
  gatsby-transformer-sharp: ^2.5.4 => 2.5.4

birkir / gatsby-source-prismic-graphql