Hugo watch not updating

Hugo watch not updating

not

Hugo server not updating

This minimal reproducible example does not require nginx. You only need to install an NPM dependency, and then delete a field in package.json to perform a specific reproducible scenario. The specific operations are as follows.


# In 2 directories, execute respectively

npm install

Use NPM directly to install the only dependency, which will install v122 and v123 in two directories under the project root directory.

Note: The downloadRepo field in the package.json file is a proxy image acceleration tool for GitHub file downloads. You need to remove this field in your country and region to install it normally, and it will not affect the use of hugo.


    "hugo-bin": {
        "buildTags": "extended",
        "downloadRepo": "https://hub.gitmirror.com/https://github.com/"
    }


    "hugo-bin": {
        "buildTags": "extended"
    }

Run the following commands in different directories through NPM to perform corresponding hugo monitoring.

v122/  npm run hugo--dev:watch

hugo v0.122.0-b9a03bd59d5f71a529acb3e33f995e0ef332b3aa+extended windows/amd64 BuildDate=2024-01-26T15:54:24Z VendorInfo=gohugoio

----------------------------------------------------

v123/  npm run hugo--dev:watch

hugo v0.123.6-92684f9a26838a46d1a81e3c250fef5207bcb735+extended windows/amd64 BuildDate=2024-02-28T18:29:40Z VendorInfo=gohugoio

Modify the home.html template file in the layouts folder. After the modification is prompted, check whether the code in the homepage under the path below has changed.


v122/layouts/home.html

v123/layouts/home.html

Directly compare whether the homepage code of these two versions has changed.


# v122 changed
v122/public/index.html

# v123 no changes
v123/public/index.html

My question is, how do I get the disk code to change for v123.

In the specific code below, there is a renderToDisk command, which has also been deleted.

In the introduction of the hugo server command, we saw such changes.

@jmooring

是否忙碌