problems launching gatsby develop
#35313
Replies: 14 comments 16 replies
-
|
I'm having a similar issue after updating gatsby to 4.11.1 and running npm outdated and updating all to Wanted using npm. Terminal says: Module not found: Error: Can't resolve '@gatsbyjs/reach-router/lib/utils' in I then use npm to install reach/router via the command npm install @reach/router The terminal says: I suspect these errors are caused by Gatsby 4.11.1 relying on [email protected] and on @reach/router, which requires [email protected]. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @albergbl, Gatsby 4.11 doesn't require React 18 (you can use older versions) and uses a fork of reach router, so you might be running into issues by installing reach router again. Difficult to say more without more information but hopefully this bit helps. If you do continue to encounter issues please create a new issue with a minimal reproduction. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @IhorFedorov7, I was not able to reproduce this. I recommend trying the command listed in the starter itself in case there's some issue with your global install of gatsby cli: |
Beta Was this translation helpful? Give feedback.
-
|
after installation: And when running gatsby develop gives the error above after npm install in the console is: And when you restart gatsby develop What I just did not try does not help. what is most interesting, everything is ok on other equipment, I upload it to git, clone it to the problem device and the problem repeats. |
Beta Was this translation helpful? Give feedback.
-
|
I am having the exact same issue when upgrading react to I have not installed reach router or the likes as explicit dependency but can see that they are |
Beta Was this translation helpful? Give feedback.
-
|
I downgraded to react 17 until this is solved 😕 Primajin/eyesbound#272 |
Beta Was this translation helpful? Give feedback.
-
|
Same issues with just updating gatsby from 4.8.0 version to 4.14.1 |
Beta Was this translation helpful? Give feedback.
-
|
And same issues with updating gatsby from 4.13.1 version to 4.14.1 |
Beta Was this translation helpful? Give feedback.
-
|
I must admit ashamed that |
Beta Was this translation helpful? Give feedback.
-
|
I am having very similar problem in this project. Which happens every time I update @gatsbyjs/reach-router from v1.3.6 to 1.3.7, then run |
Beta Was this translation helpful? Give feedback.
-
|
4 months later this is still consistently happening |
Beta Was this translation helpful? Give feedback.
-
|
I was having the same problem. Turns out that I was unable to make
rm -r package-lock.json node_modules .cache
pnpm i
pnpm add -D gatsby-plugin-pnpm
// gatsby-config.js
module.exports = {
plugins: [
`gatsby-plugin-pnpm`,
...
]
}Now everything is working again |
Beta Was this translation helpful? Give feedback.
-
|
@javiertury While this does work to resolve builds locally but depending on the CI/CD process you have it may not. In my case Netlify is not having it with pnpm builds (npx pnpm build, pnpm build || (npm install pnpm && pnpm build), repeat random search query suggestions for builds). Any thought on getting it working with pnpm? |
Beta Was this translation helpful? Give feedback.
-
|
I suspect there is something wrong with your CI/CD pipeline. Make sure to call Do not use |
Beta Was this translation helpful? Give feedback.
-
|
@javiertury Alright I can try modifying the commands. At the moment I "resolved" the issue by installing all the packages that Gatsby complains it really wants and that works but isn't ideal. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I got this working with Using Example of warnings:
Thanks for sharing! |
Beta Was this translation helpful? Give feedback.
-
|
This is annoying. Every go at updating dependencies is russian roulette. Whenever this error appears, I end up spending hours trying to get the project to work again. And this has been ongoing for over 4 months now. The issue is so bad, I feel the only way to get rid of it is migrating away from gatsby. Why was this issue moved to a discussion? |
Beta Was this translation helpful? Give feedback.
-
|
@barbalex How did you end up getting everything back up and running? I've had to do this same song and dance before as well but have no idea what actually fixes things. Tried pnpm as suggested above which does work to resolve builds locally but depending on the CI/CD process you have it may not. In my case Netlify is not having it with pnpm builds / npx pnpm build etc. |
Beta Was this translation helpful? Give feedback.
-
|
I reverted to previous yarn.lock file. |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, so sorry you are experiencing lingering issues with this. I originally moved this to a discussion when it was probably better that I left it as an issue and requested for a minimal reproduction. Over time it's gathered various comments from people that have landed here, but it's difficult to separate signal from noise. If you're still experiencing issues, please open a new issue with a minimal reproduction and we'll do our best to triage. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
This happens in only one of my projects. Which is basically huge. Sorry to say it is not possible for me to build a minimal reproduction. But yes, I spent again 5 hours today fighting this dragon. With no idea when or if the project will ever run again |
Beta Was this translation helpful? Give feedback.
-
|
Today I updated @gatsbyjs/reach-router to 1.3.10-no-navigate.4 and gatsby 4.21.1 (including all the other gatsby stuff) and now get a slightly different error: So instead of Here the complete error: I tried:
I really do not know why I keep getting these errors almost every time I update gatsby related libraries. |
Beta Was this translation helpful? Give feedback.
-
|
You shouldn't need to install those dependencies separately, especially not versions that are not supposed to be used by end users like you. With |
Beta Was this translation helpful? Give feedback.
-
|
Seems that yarn upgrade-interactive lead me to install that version of reach-router without noticing. |
Beta Was this translation helpful? Give feedback.
-
|
Similar to #35313 , downgrading to My situation is pretty niche I think but I wanted to share in case it helps someone else. I'm using yarn workspaces (yarn version
The issue for me seemed to be that strapi uses react 17. So I was able to solve the problem by either:
|
Beta Was this translation helpful? Give feedback.
-
|
I'm getting issue running before that I had to force install gatsby-scripts, gatsby-react-router-scroll, gatsby-link into package.json, I have It is just not looking down the node_modules tree. Please fix. |
Beta Was this translation helpful? Give feedback.
-
|
Found the solution, described it in my latest issue: #36565 |
Beta Was this translation helpful? Give feedback.
-
|
Same problem here when we upgrade from React 17.0.2 to 18.2. Any solution to this? Since there are several open issues on Github with the same problem. |
Beta Was this translation helpful? Give feedback.
-
|
This worked for me in I use PNPM. |
Beta Was this translation helpful? Give feedback.
-
|
Please try installing the missing packages using npn install --force. It should help. |
Beta Was this translation helpful? Give feedback.
-
Preliminary Checks
Description
by installing npm install -g gatsby-cli
after i created a new project gatsby new blog
I have a folder but without node_modules
when running gatsby develop gives an error and recommends installing manually npm install after repeated gatsby develop starts to give such errors
ERROR #98124 WEBPACK
Generating development SSR bundle failed
Can't resolve '@reach/router/lib/utils' in 'C:\Users\ihorf\Desktop\Igor\WORK\GATSBY\adlockBlog.cache'
If you're trying to use a package make sure that '@reach/router/lib/utils' is installed. If you're trying to
use a local file to make sure that the path is correct.
File: .cache\find-path.js
ERROR #98124 WEBPACK
Generating development SSR bundle failed
Can't resolve 'gatsby-link' in 'C:\Users\ihorf\Desktop\Igor\WORK\GATSBY\adlockBlog.cache'
If you're trying to use a package make sure that 'gatsby-link' is installed. If you're trying to use a local
file make sure that the path is correct.
File: .cache\gatsby-browser-entry.js
ERROR #98124 WEBPACK
Generating development SSR bundle failed
Can't resolve 'gatsby-react-router-scroll' in 'C:\Users\ihorf\Desktop\Igor\WORK\GATSBY\adlockBlog.cache'
If you're trying to use a package make sure that 'gatsby-react-router-scroll' is installed. If you're trying
to use a local file make sure that the path is correct
.
Reproduction Link
Steps to Reproduce
Expected Result
I'm waiting for help and solving the problem, because I really want to create a project on Gatsby js
Actual Result
error
Environment
System: OS: Windows 10 10.0.19044 CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz Binaries: Node: 16.13.1 - C:\Program Files\nodejs\node.EXE npm: 8.2.0 - C:\Program Files\nodejs\npm.CMD Languages: Python: 3.9.2 Browsers: Edge: Spartan (44.19041.1266.0), Chromium (99.0.1150.55) npmPackages: gatsby: ^2.19.38 => 2.32.13 gatsby-link: ^4.11.0 => 4.11.0 gatsby-page-utils: ^2.11.0 => 2.11.0 gatsby-plugin-gatsby-cloud: ^1.0.2 => 1.0.2 gatsby-plugin-image: ^0.7.2 => 0.7.2 gatsby-plugin-manifest: ^2.6.1 => 2.6.1 gatsby-plugin-offline: ^3.10.2 => 3.10.2 gatsby-plugin-react-helmet: ^3.10.0 => 3.10.0 gatsby-plugin-sharp: ^2.14.4 => 2.14.4 gatsby-react-router-scroll: ^5.11.0 => 5.11.0 gatsby-source-filesystem: ^2.11.1 => 2.11.1 gatsby-transformer-sharp: ^2.12.1 => 2.12.1 npmGlobalPackages: gatsby: 4.11.0Config Flags
No response
Beta Was this translation helpful? Give feedback.
All reactions