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.

mdx-deck start error with 'TypeError: Cannot read property 'internal' of null'

See original GitHub issue

I’m creating a deck using the example from Zeit’s now-examples repository.

I can start a development server correctly and see the success: Building development bundle output from Gatsby, however as soon as I change a file the development server crashes with this error:

  TypeError: Cannot read property 'internal' of null
  
  - gen-mdx.js:48 payloadCacheKey
    [javascript-slides]/[gatsby-plugin-mdx]/utils/gen-mdx.js:48:46
  
  - gen-mdx.js:51 genMDX
    [javascript-slides]/[gatsby-plugin-mdx]/utils/gen-mdx.js:51:43
  
  - source-nodes.js:108 processMDX
    [javascript-slides]/[gatsby-plugin-mdx]/gatsby/source-nodes.js:108:5
  
  - source-nodes.js:158 resolve
    [javascript-slides]/[gatsby-plugin-mdx]/gatsby/source-nodes.js:158:35
  
  - gatsby-node.js:40 
    [javascript-slides]/[gatsby-theme-mdx-deck]/gatsby-node.js:40:24
  
  - gatsby-node.js:47 resolveTitle
    [javascript-slides]/[gatsby-theme-mdx-deck]/gatsby-node.js:47:60
  

not finished createPages - 0.077s


——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
3 pages                                                                    In Progress                                                                    mdx-deck
Error: Command failed with exit code 1 (EPERM): gatsby develop --host localhost --port 8000 --open
    at makeError (/Users/jackleslie/Desktop/Talks/javascript-slides/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/Users/jackleslie/Desktop/Talks/javascript-slides/node_modules/execa/index.js:112:26)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Here’s my project for reference, nothing much to see at the moment

Issue Analytics

State:
Created 4 years ago
Reactions:20
Comments:18 (4 by maintainers)

Top GitHub Comments

6reactions

mlouagecommented, Jan 3, 2020

Same here, the fix does not work for “mdx-deck”: “^3.0.13”

I added the following and it worked

“resolutions”: { “mdx-deck/**/gatsby”: “2.18.4” },

I’m using yarn.

5reactions

trevordmillercommented, Jan 23, 2020

I would suggest keeping this issue open until a fix is in place in the repo itself, not specific to pinning a sub-dependency version and using yarn. Looks like https://github.com/jxnblk/mdx-deck/pull/603 fixes it. Also might be a duplicate of https://github.com/jxnblk/mdx-deck/issues/595.

Top Results From Across the Web

Cannot read properties of null (reading 'default') in Next.js ...

js application started throwing TypeError: Cannot read properties of null (reading 'default') without me changing anything in my code where I'm rendering some ......

Cannot read properties of null (reading '_doc') : r/graphql

I'm running a query in GraphQL and getting this error: { "errors": [ { "message": "Cannot read properties of null (reading '_doc')", ...

Fix Cannot Set Property of Null Error in JavaScript - YouTube

Check us out at https://www.skillforge.com The " cannot set property of null " error is a very common JavaScript issue that you may...

missing required prop: "chartdata" - You.com | The AI Search ...

The computed property "chartData" is already defined as a prop. I am a novice in this framework and I ... Favicon for github....

3 Minutes with Kent - Briefs

So you can't avoid adding complexity when you start abstracting ... is that there I set up a postgres database inside a Docker...