file name too long

[Perrywzp]

Describe the bug

as we create too deep folders , appear the fault : file name too long while build

Reproduction

create too deep folders

Expected behavior

except can build success, even zhe folders is deep and each folder name is long

System Info

System:
    OS: Windows 10 10.0.16299
    CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
    Memory: 5.00 GB / 15.89 GB
  Binaries:
    Node: 20.9.0 - D:\program\nvm1.1.11\nodejs\node.EXE
    npm: 10.1.0 - D:\program\nvm1.1.11\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (41.16299.1480.0)
    Internet Explorer: 11.0.16299.371
  npmPackages:
    vitepress: ^1.0.0-rc.44 => 1.0.1

Additional context

No response

Validations

• [X] Check if you're on the latest VitePress version.
• [X] Follow our Code of Conduct
• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[brc-dd]

Enable this - https://www.microfocus.com/documentation/filr/filr-4/filr-desktop/t47bx2ogpfz7.html

[Perrywzp]

how can i set in centos7, because i set gitlabCICD on it . it appear this fault too.

[brc-dd]

On centos this shouldn't be happening unless you are using a filesystem that's limiting the path length. Can you post the exact error with stack trace and system information from the machine where the error is actually happening.

as we create too deep folders

How deep exactly are you talking about? Can you share the output of getconf -a . from your project directory.

[Perrywzp]

so sorry , like this picture, because we use chinese name folders, it`s deep and long.

[brc-dd]

Ah, now I understand. The name is containing the joined path which may exceed NAME_MAX.

[Perrywzp]

can this question be fixed quickly? very thanks!

[brc-dd]

Ah it's not that easy. We'll need to change whole chunk resolution logic to make this work. I'd recommend switching to some other tool for now if this is urgent.