I updated my local environment to 0.79 recently and just been trying to finish up a new blog post… but running Hugo server is taking a bit longer than I’d expect and now its not picking up changes in the content i’m trying to proof-read and finish.
I’m stuck as to what is broke - any ideas please?
“Proof Reading” sounds to me like you have a tool or an editor or an IDE running over these files. There could be an issue with concurrent read/write activity by multiple programs that slow things down or something even locking the files for itself. Most times it’s the other software, not Hugo But as @divinerites said - more information needed.
The aim of most “package systems” is to give you ALWAYS the latest version of something, while keeping compatible amongst each of the used packages. So the concept of downgrading is not really something that is there. But you can in most of these systems make a version “static” or “fixed”.
Looks like you have to find the hash of the version you want to install and then… well… install it. The fixing in brew is then called “pinning” (everyone has a different nice name for the bad things they do).
I am using Webstorm (and also Pycharm for the Hugo comment system I am writing) with the latest Hugo plugin and I cannot confirm this. Live udpates are going as fast as the wind. VS Code isn’t the fastest of IDE’s, can you try running the development server on a shell outside of VS Code and see if this reproduces?
If yes, do you have the files on a HDD or SSD? If HDD, any chance it has a low cache, such as 16MB or something? If possible, look at how much cache it has. HDD cache sizes ARE important.
There are several posts in recent months about issues with livereload in connection with VSCode. Not sure if they ever got solved, but the mention of VSCode is a trigger word for “disable all unnecessary plugins and see what’s happening” and “test outside of the IDE and see if it re-occurs”.
There is no helpdesk. Just people concerned that issues with Hugo make it look bad
I think we (or someone connected to Hugo) should connect with the VSCode people and have a talk about this. It’s relatively obvious that there is something going on that might be solved only on “developer to developer” base.