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.
[gatsby-cli] Error: Cannot find module '../ink/components/progress-bar'
See original GitHub issueDescription
After updating “gatsby-cli”: “^2.10.3”, it throws the following error.
Error: Cannot find module '../ink/components/progress-bar'
Steps to reproduce
Update gatsby-cli to ^2.10.3 and run gatsby develop or any other gatsby ... command
Expected result
Gatsby CLI should run every gatsby ... command as usual instead of breaking.
Actual result
▶ gatsby develop
/usr/local/lib/node_modules/gatsby-cli/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
throw ex;
^
Error: Cannot find module '../ink/components/progress-bar'
Require stack:
- /usr/local/lib/node_modules/gatsby-cli/lib/reporter/loggers/ink/cli.js
- /usr/local/lib/node_modules/gatsby-cli/lib/reporter/loggers/ink/index.js
- /usr/local/lib/node_modules/gatsby-cli/lib/reporter/index.js
- /usr/local/lib/node_modules/gatsby-cli/lib/create-cli.js
- /usr/local/lib/node_modules/gatsby-cli/lib/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:794:15)
at Function.Module._load (internal/modules/cjs/loader.js:687:27)
at Module.require (internal/modules/cjs/loader.js:849:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.<anonymous> (/usr/local/lib/node_modules/gatsby-cli/lib/reporter/loggers/ink/cli.js:22:20)
at Module._compile (internal/modules/cjs/loader.js:956:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
at Module.load (internal/modules/cjs/loader.js:812:32)
at Function.Module._load (internal/modules/cjs/loader.js:724:14)
at Module.require (internal/modules/cjs/loader.js:849:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/usr/local/lib/node_modules/gatsby-cli/lib/reporter/loggers/ink/cli.js',
'/usr/local/lib/node_modules/gatsby-cli/lib/reporter/loggers/ink/index.js',
'/usr/local/lib/node_modules/gatsby-cli/lib/reporter/index.js',
'/usr/local/lib/node_modules/gatsby-cli/lib/create-cli.js',
'/usr/local/lib/node_modules/gatsby-cli/lib/index.js'
]
}
Environment
Unfortunately gatsby info --clipboard doesn’t work either.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:51
- Comments:46 (7 by maintainers)
Top Results From Across the Web
Error: Cannot find module 'gatsby-cli/lib/reporter' - Stack ...
Already deleted node-modules and reinstalled using npm. Tried installing Gatsby-Cli as a separate module but that just causes more gatsby-cli ...
Read more >Gatsby, fix the "cannot find module gatsby-cli/lib/reporter" error
I created a site using Gatsby and I ran gatsby develop to start a local server. After a few searches across GitHub and...
Read more >Eva - includeJS.dev 🏳️ on Twitter: "Well this was cool! After ...
Description After updating "gatsby-cli": "^2.10.3", it throws the following error. Error: Cannot find module '../ink/components/progress-bar' Ste.
Read more >Gatsby Changelog | 5.3.0
By using a new <Slice /> React component in combination with a src/slices directory or createSlice API for common UI features, Gatsby will...
Read more >ink - npm
Build and test your CLI output using components. Build Status npm. Ink provides the same component-based UI building experience that React ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve identified this and have a hotfix coming. No worries @herecydev, but thank you!
OOF! So sorry about this everyone… I’ve released a new version that fixes this. Please update.
Again, I’m so sorry for the damage this caused in lost time and hair-pulling! 😢 💜