Why can't the images be parsed when the folder name where they are stored is 'js'?

[abs612]

Introducing this image in the MD document, as follows:

<img src=".\images\js\函数-柯里化函数-001.png" style="zoom:80%;" />

There are no issues when using npm run docs:dev locally, the document is converted to HTML and the images are normal. However, when using GitHub Pages, the images cannot be parsed.

Run npm run docs:build

> docs:build
> vitepress build docs


  vitepress v1.1.3

- building client + server bundles...
x Build failed in 7.4[6](https://github.com/msar212/yxtsBlog/actions/runs/8824747632/job/24227768035#step:6:7)s
✖ building client + server bundles...
build error:
RollupError: Could not resolve "./images/js/函数-柯里化函数-001.png" from "docs/pages/前端/阶段一：三驾马车/3. JavaScript/1. JavaScript笔记.md"
file: /home/runner/work/yxtsBlog/yxtsBlog/docs/pages/前端/阶段一：三驾马车/3. JavaScript/1. JavaScript笔记.md
    at getRollupError (file:///home/runner/work/yxtsBlog/yxtsBlog/node_modules/rollup/dist/es/shared/parseAst.js:394:41)
    at error (file:///home/runner/work/yxtsBlog/yxtsBlog/node_modules/rollup/dist/es/shared/parseAst.js:390:42)
    at ModuleLoader.handleInvalidResolvedId (file:///home/runner/work/yxtsBlog/yxtsBlog/node_modules/rollup/dist/es/shared/node-entry.js:1916[7](https://github.com/msar212/yxtsBlog/actions/runs/8824747632/job/24227768035#step:6:8):24)
    at file:///home/runner/work/yxtsBlog/yxtsBlog/node_modules/rollup/dist/es/shared/node-entry.js:1[9](https://github.com/msar212/yxtsBlog/actions/runs/8824747632/job/24227768035#step:6:10)127:26
Error: Process completed with exit code 1.

I spent a long time discovering this issue because the folder name is 'js'.

[brc-dd]

Not reproducible at my end. Can you share your repo where this happening?

[abs612]

From last night to this morning, it was all about this issue. I just checked and nothing was changed, but surprisingly, the GitHub Pages compilation succeeded. It's really strange.

I really appreciate your answers, master.

[abs612]

Not reproducible at my end. Can you share your repo where this happening?