Start script fails on building frontend with yarn

[Mereck13579]

Tripled checked dependencies (shown below) but everything seems to check out. I even downgraded node back to 24.12.0 instead of 25.x just in case, but I keep hitting the same error.
Also tried running it as administrator, got the same result.

I'm running Windows 10 22H2

H:\SillyTavern\SillyInnKeeper>start.bat
========================================
Starting SillyInnkeeper Project
========================================

[0/7] Checking package manager...
Using yarn as package manager

[1/7] Checking backend dependencies (server)...
Backend dependencies already installed, skipping...

[2/7] Checking frontend dependencies (client)...
Installing frontend dependencies with yarn...
➤ YN0050: The --prefer-offline flag is deprecated; use the --cached flag with 'yarn add' instead

[3/7] Checking frontend build...
Building frontend with yarn...
Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation)

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] <scriptName> ...
Error building frontend!
Press any key to continue . . .

H:\SillyTavern\SillyInnKeeper>npm -v
11.6.2

H:\SillyTavern\SillyInnKeeper>node -v
v24.12.0

H:\SillyTavern\SillyInnKeeper>yarn -v
4.12.0

H:\SillyTavern\SillyInnKeeper>

Edits: fixed quotes... was tired. Added Win version.

[dmitryplyaskin]

Try running start-had.bat; if that doesn't work, try manually building the project by installing the dependencies in the client and server folders and then building the project.

It seems this problem occurs too often, and I need to modify the files to get the project running.

[UnlikelySemicolon]

Using start-hard.bat resolved this for me. An initial npm install had failed.

[Mereck13579]

Same here, start-hard.bat managed to get it started and working. I will keep the issue opened since the regular start isn't working but feel free to close it if you consider the start-hard as a fix.

[weyw]

Can confirm had to use start-hard.bat after a fresh clone