search

ericalli / static-site-boilerplate

A better workflow for building modern static websites.
http://staticsiteboilerplate.com
MIT License
1.73k stars 165 forks source link

Changes to files do not reflect in the browser #4

Closed vladzima closed 5 years ago

vladzima commented 5 years ago

Describe the bug Dev server. Changes to files do not reflect in the browser neither with hot reload nor with manual. Only relaunching server works.

To Reproduce Steps to reproduce the behavior:

  1. Install new boilerplate.
  2. Make changed to index.html.
  3. See no changes to the index page in the browser.

Expected behavior Reflecting changes to the file at least with manual page reload.

Desktop (please complete the following information):

ericalli commented 5 years ago

Hmm, I'm not able to reproduce this on my end. If possible, could you update your Node and NPM versions and reinstall the packages using npm install? I'm almost certain that will resolve your issue.

kalpsjo commented 5 years ago

I too have this issue. I have reinstalled Node using Brew and ran nmp install.

OS: El Capitan Browser: Chrome 71.0.3578.98 Node: 11.6.0 Npm 6.4.1

w-stegmann commented 5 years ago

Same issue right here. Updates and a clean install didn't help.

OS: macOS Mojave 10.14.2 Browser: Chrome 71.0.3578.98 Node: 11.7.0 npm: 6.5.0

vladzima commented 5 years ago

Yes, same, updates certainly didn't help.

w-stegmann commented 5 years ago

The update of webpack-dev-server 3.1.10 to 3.1.14 fucked it up. A downgrade temporarily fixed the issue for me.

  1. Open package.json
  2. Find "webpack-dev-server": "^3.1.14"
  3. Replace with "webpack-dev-server": "^3.1.10"
ericalli commented 5 years ago

@w-stegmann is right. The update to webpack-dev-server is causing the issue -- I committed a downgrade until a compatible version is released.

davidholtz commented 5 years ago

I am also having this issue, despite the webpack-dev-server downgrade to "^3.1.10", which I do see.

OS: macOS Mojave 10.14.3 Browser: Firefox 65, but also happening in Chrome 71.0.3578.98 Node: 10.5.0 npm: 6.1.0

davidholtz commented 5 years ago

Started over after Installing Node 11.7.0 / npm 6.5.0, but didn't make a difference.

w-stegmann commented 5 years ago

Have you executed npm install in the folder after changing the package.json?

davidholtz commented 5 years ago

Yeah, my process has been to remove the folder completely, use nvm to install/use a different/newer version, then follow Eric's steps from the beginning: 1. clone, 2. npm install, 3. npm run start.

davidholtz commented 5 years ago

The latest version of Eric's package.json file is calling webpack-dev-server 3.1.10 by default.

davidholtz commented 5 years ago

Hi. Just wanted to see if anyone else has been experiencing this issue or has any other advice for me. I am excited to jump in and use this thing.

susan8098 commented 5 years ago

I just did a fresh install of this and having the same problem. The "webpack-dev-server" is set to "^3.1.10"

ericalli commented 5 years ago

@susan8098 This should be fixed in the latest release v1.1.0