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

Livereload not working on 1.10.0 build #1508

Closed
Triskae opened this issue May 22, 2019 · 4 comments
Closed

Livereload not working on 1.10.0 build #1508

Triskae opened this issue May 22, 2019 · 4 comments

Comments

@Triskae
Copy link
Contributor

Triskae commented May 22, 2019

🐛 Bug Report

When I run wpm start (or even yarn start) the live reload server start but when I try to modify something inside the website folder, the page reloads but nothing is update. It seems like chnages on the files triggered the live reload but nothing is rebuilt.

Have you read the Contributing Guidelines on issues?

Yes

To Reproduce

  1. npm install --global docusaurus-init
  2. npm start inside the website folder

Expected behavior

The server is suposed to start, and when I do changes inside the website folder, the webpage is suposed to reload with the new changes.
e.g When I change a label on the headerLinks section, changes are suposed to be visible.

Actual Behavior

The server starts well, but when a modify something, the page relaod, but the changes are not visible. I need to CTRL+C the npm start process to restart it to see the changes.

Reproducible Demo

You can try to reproduce the this issue on my repo:
https://github.com/Triskae/Messosaurus

@endiliey
Copy link
Contributor

That's due to #267 bug of siteconfig not being able to reload.

@Triskae
Copy link
Contributor Author

Triskae commented May 22, 2019

Ok thanks, I saw that you fixed this bug right ?

@endiliey
Copy link
Contributor

yeah #1509

@malek0512
Copy link

malek0512 commented Apr 22, 2020

Hello @endiliey this issue still occurs on 1.14.4 version.
I am not sure to understand what was the fix on 1.10.0 version.
Is there any solution for this issue ?

Thank you in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants