Mdx-deck: Hot reloading is not working

[NicholasPeretti]

Environment

Machine: MacBook Pro 15" 2018
Browser: Chrome (version 76.0.3809.132)

Description

I was trying this awesome package in order to create some slides for my tech talk.
I've followed the instructions on the readme of this repo, so my files are:

• package.json
• deck.mdx
• yarn.lock
• node_modules
  which is pretty standard. The start script is mdx-deck deck.mdx.

What should happen?

When I run yarn start, I expect the program to start, build the app and serve it in the 8000 port of my browser. Furthermore, I want to see hot-reloaded changes every time I edit my deck.mdx

What happen instead?

The program creates the first build form the files and serves it correctly on the port 8000 of my browser.
Anyhow, when I change a file I can see from the console that Webpack recompile the code but no changes appear on my browser page.
At this point I launch a refresh of the page, expecting the changes to be shown on the page. One again I'm not able to see them.

In order to actually navigate an updated version of my app I need to stop the program and re-run yarn start, which is painful.

[NicholasPeretti]

After some tests I've noticed that, if I have more slides, I need to edit the first one to trigger the hot reloading. Otherwise I won't see the edit, just like described in #474 .

Anyway, at the beginning I had only one slide and the hot reloading wasn't working in there.

I've tried to create a sandbox and tried to reproduce the error but everything seems to work in there. I'll create a repo on GitHub in order to allow you to reproduce the error on your machines.

[NicholasPeretti]

I think I know what's happening here

I was working without a git repo in the project folder. As soon as I created it everything started working normally.

I guess hot reloading uses git APIs in order to detect changes, I don't have any clue on this.
Anyhow, this issue could be related to #474

[jonsherrard]

@NicholasPeretti just out of interest, are using VSCode?

[NicholasPeretti]

@jonsherrard Yes, do you think it's related to the issue?

[jonsherrard]

@NicholasPeretti - I don't think it's a git issue as my repro on #474 is on Github! Not VSCode issue either as I just moved to an entirely different machine that only has Vim on it, and I'm getting the same issue there.

[jonsherrard]

To fix your mdx-deck v3 project temporarily, run the following commands in your presentation project:

rm -rf node_modules
npm install [email protected] -D --save-exact
npm install

[NicholasPeretti]

@jonsherrard Thank you for finding the time to look into it. I've tried your solution and now I have the exact same problem of #474, it hot-reloads only when the first slide changes.

[jonsherrard]

Could you not get it to work by pinning the Gatsby version?

[NicholasPeretti]

Nope.

I've tried to delete both the node_modules directory and the yarn.lock file (I use yarn).
Then I've typed:
yarn add [email protected] --exact
yarn add mdx-deck

After that I've tried to start the project with yarn start and I have the same problem described in #474

[jonsherrard]

And if you go into node_modules/gatsby and open package.json the version is 2.14.7?

[NicholasPeretti]

@jonsherrard Yes, it is

[ravanscafi]

I'm having the same issue, I'm unable to make it work :cry:

[jxnblk]

Duplicate of #474