question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Cannot find module 'gatsby/dist/utils/create-content-digest'

See original GitHub issue

Description

When I run $ gatsby build it throws the below error.

Steps to reproduce

  • Update gatsby
  • Run gatsby build

I cannot publish my current project publicly and am unable to reproduce with a simple starter project.

Expected result

Gatsby should build the project (same as in v2.10.5).

Actual result

After updating from v2.10.5 to v2.13.41 I get the following error after running $ gatsby build:

> gatsby build

success open and validate gatsby-configs - 0.131 s

 ERROR

Error in "/Users/zoec/Desktop/pro-com-homepage/node_modules/gatsby-plugin-manifest/gatsby-node.js": Cannot find module 'gatsby/dist/utils/create-content-digest'



  Error: Cannot find module 'gatsby/dist/utils/create-content-digest'

  - loader.js:581 Function.Module._resolveFilename
    internal/modules/cjs/loader.js:581:15

  - loader.js:507 Function.Module._load
    internal/modules/cjs/loader.js:507:25

  - loader.js:637 Module.require
    internal/modules/cjs/loader.js:637:17

  - v8-compile-cache.js:159 require
    [pro-com-homepage]/[v8-compile-cache]/v8-compile-cache.js:159:20

  - gatsby-node.js:19 Object.<anonymous>
    [pro-com-homepage]/[gatsby-plugin-manifest]/gatsby-node.js:19:51

  - v8-compile-cache.js:178 Module._compile
    [pro-com-homepage]/[v8-compile-cache]/v8-compile-cache.js:178:30

  - loader.js:700 Object.Module._extensions..js
    internal/modules/cjs/loader.js:700:10

  - loader.js:599 Module.load
    internal/modules/cjs/loader.js:599:32

  - loader.js:538 tryModuleLoad
    internal/modules/cjs/loader.js:538:12

  - loader.js:530 Function.Module._load
    internal/modules/cjs/loader.js:530:3

  - loader.js:637 Module.require
    internal/modules/cjs/loader.js:637:17

  - v8-compile-cache.js:159 require
    [pro-com-homepage]/[v8-compile-cache]/v8-compile-cache.js:159:20

  - resolve-module-exports.js:126 module.exports
    [pro-com-homepage]/[gatsby]/dist/bootstrap/resolve-module-exports.js:126:26

  - validate.js:124 flattenedPlugins.forEach.plugin
    [pro-com-homepage]/[gatsby]/dist/bootstrap/load-plugins/validate.js:124:31

  - Array.forEach

  - validate.js:117 collatePluginAPIs
    [pro-com-homepage]/[gatsby]/dist/bootstrap/load-plugins/validate.js:117:20

Environment


  System:
    OS: macOS 10.14.5
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.11.0 - ~/.nvm/versions/node/v10.11.0/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.11.0/bin/npm
  Languages:
    Python: 2.7.10 - /usr/bin/python
  Browsers:
    Chrome: 75.0.3770.100
    Safari: 12.1.1
  npmPackages:
    gatsby: ^2.13.41 => 2.13.41 
    gatsby-image: 2.2.3 => 2.2.3 
    gatsby-plugin-env-variables: 1.0.1 => 1.0.1 
    gatsby-plugin-google-analytics: 2.1.0 => 2.1.0 
    gatsby-plugin-manifest: 2.2.0 => 2.2.0 
    gatsby-plugin-material-ui: 2.0.1 => 2.0.1 
    gatsby-plugin-offline: 2.2.0 => 2.2.0 
    gatsby-plugin-react-helmet: 3.1.0 => 3.1.0 
    gatsby-plugin-segment-js: 3.0.1 => 3.0.1 
    gatsby-plugin-sharp: 2.2.1 => 2.2.1 
    gatsby-plugin-sitemap: 2.2.0 => 2.2.0 
    gatsby-source-prismic: 2.2.0 => 2.2.0 
    gatsby-transformer-sharp: 2.2.0 => 2.2.0 
  npmGlobalPackages:
    gatsby-cli: 2.7.20

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:11 (2 by maintainers)

github_iconTop GitHub Comments

23reactions
DSchaucommented, Jul 26, 2019

@zoecarver thanks for offering! Let’s go ahead and close.

For anyone else:

npm i gatsby-plugin-manifest

should do the trick. Thanks!

20reactions
zoecarvercommented, Jul 26, 2019

Yep, updating gatsby-plugin-manifest fixed the issue. Want me to close this?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Building static HTML failed when you createContext ... - GitHub
My site would work fine with gatsby develop but failed using gatsby build with the error: "WebpackError: TypeError: Cannot read property of ...
Read more >
Gatsby - Uncaught TypeError - Context/build problem
Everything is working fine with "gatsby develop", but when I run "gatsby build" I get an error: "WebpackError: TypeError: Cannot destructure ...
Read more >
gatsby @ 2.1.4 .. 2.1.27 - Package Diff
There was an error compiling the html.js component for the development server. - See our docs page on debugging HTML builds for help...
Read more >
All Problems Tagged With Whatever - Code Grepper
Perform Breadth First Traversal on the given graph. module not found: error: can't resolve '@emotion/react' in '/users/ishangupta/go/src/github.com/ ...
Read more >
Files changed (172) - Renovate Bot Package Diff
+ - **gatsby:** Recognise null pages as not found ... module.exports = Object.assign; ... console.error(`Could not connect to socket.io on dev server.`);.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found