Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gatsby develop error: "gatsby-plugin-mdx" threw an error while running the onCreateNode lifecycle #25612

Closed
Louisrobertson20 opened this issue Jul 8, 2020 · 3 comments
Labels
stale? Issue that may be closed soon due to the original author not responding any more. type: bug An issue or pull request relating to a bug in Gatsby

Comments

@Louisrobertson20
Copy link

Description

After pulling the Gatsby Personal Starter Blog and running gatsby develop, I am getting the following error: "gatsby-plugin-mdx" threw an error while running the onCreateNode lifecycle: Cannot find module 'gatsby-remark-vscode'

Steps to reproduce

  1. gatsby new [your-project-name] https://github.com/thomaswangio/gatsby-personal-starter-blog
  2. cd to project
  3. npm install sharp
  4. gatsby develop

Expected result

What should happen?

I should be able to start the site on local host 8000

Actual result

What happened.

Error appears in CLI as above.

Environment

System:
OS: Windows 10 10.0.18362
CPU: (4) x64 Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz
Binaries:
Node: 14.1.0 - C:\Program Files\nodejs\node.EXE
npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.18362.449.0
npmPackages:
gatsby: ^2.23.11 => 2.23.22
gatsby-image: ^2.0.39 => 2.4.12
gatsby-plugin-feed-mdx: ^1.0.0 => 1.0.1
gatsby-plugin-google-analytics: ^2.0.18 => 2.3.10
gatsby-plugin-manifest: ^2.0.29 => 2.4.17
gatsby-plugin-mdx: ^1.2.14 => 1.2.22
gatsby-plugin-netlify-cms: ^4.3.7 => 4.3.10
gatsby-plugin-offline: ^2.0.25 => 2.2.10
gatsby-plugin-react-helmet: ^3.0.12 => 3.3.9
gatsby-plugin-sharp: ^2.0.35 => 2.6.18
gatsby-plugin-styled-components: ^3.0.7 => 3.3.9
gatsby-plugin-typography: ^2.2.13 => 2.5.9
gatsby-remark-copy-linked-files: ^2.0.11 => 2.3.10
gatsby-remark-images: ^3.3.9 => 3.3.17
gatsby-remark-responsive-iframe: ^2.1.1 => 2.4.10
gatsby-remark-smartypants: ^2.0.9 => 2.3.9
gatsby-source-filesystem: ^2.0.29 => 2.3.18
gatsby-transformer-sharp: ^2.1.18 => 2.5.10
npmGlobalPackages:
gatsby-cli: 2.12.59

@Louisrobertson20 Louisrobertson20 added the type: bug An issue or pull request relating to a bug in Gatsby label Jul 8, 2020
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Jul 8, 2020
@graysonhicks
Copy link
Contributor

Hi @Louisrobertson20 I believe this is a duplicate of an issue on that starter repo itself: https://github.com/thomaswang/gatsby-personal-starter-blog/issues/8. This is not an issue with Gatsby itself, but something with how that community starter has its dependencies.

@graysonhicks graysonhicks added topic: starters and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Jul 8, 2020
@github-actions
Copy link

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

@github-actions github-actions bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Jul 29, 2020
@github-actions
Copy link

github-actions bot commented Aug 8, 2020

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale? Issue that may be closed soon due to the original author not responding any more. type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
Development

No branches or pull requests

3 participants