Build error: "Cannot find H:\workspaces\plate\plate\packages\test-utils\src\index.ts"

[jss-less-step]

Hello, I'm a newcomer using PlateJS. Following the "contributing guide," I pulled the source code using Git, and after running yarn install to complete the dependency installation, I encountered an error when using the yarn build command. The error message is shown in the attached image. I am on the main branch, and my development environment is Windows. I wonder if this project does not support development on Windows, and how can I resolve the corresponding build issue?

Funding

• You can sponsor this specific effort via a Polar.sh pledge below
• We receive the pledge once the issue is completed & verified

[12joan]

Does the path it's complaining about exist?

You might have better luck using a Unix-style terminal, like Git Bash.

[moyang2024]

That is bad

[12joan]

@zbeyens and myself (the two maintainers of Plate) are macOS users, and Plate is an exceedingly complex repo, so ensuring perfect compatibility with Windows systems isn't really feasible for us. If you want to fix the issue yourself in a PR, go ahead.

[moyang2024]

Thank you.

[jss-less-step]

哥们要不加个好友，我也在做这块内容，有时间一起讨论一下？

[moyang2024]

好 qq1542051400

[YingQQQ]

I'm running into the same problem with 'yarn build' on both macOS and Windows 10. It's really confusing, especially since the missing files are clearly there.

[12joan]

@JSSMaybeUFather @moyang-pro @YingQQQ Can everyone share the output of node --version and yarn --version?

The fact that multiple people have started seeing this at the same time, but not everyone has, suggests a recent regression in a third-party tool to me.

I'm using Node v20.5.1 and yarn 4.0.0-rc.43.

[YingQQQ]

Node v21.2.0 and yarn 4.0.0-rc.43.

[jss-less-step]

Node v18.17.0 and yarn 4.0.0-rc.43.

[moyang2024]

Node v16.19.1 and yarn 4.0.0-rc.43.

[uchechiukpa]

Expressing the same error too
Node v18.18.0 and yarn 4.0.0-rc.43

[12joan]

@YingQQQ You mentioned that you saw this issue on macOS, but as far as I'm aware, no one else has. Can you post the output you get when the error happens for you on macOS?