ai-toolkit icon indicating copy to clipboard operation
ai-toolkit copied to clipboard

Error: EISDIR: illegal operation on a directory

Open brazilgithub opened this issue 5 months ago • 4 comments

I'm trying to run the code, but I have below. Anyone else having this issue? How can I help?

(venv) I:\WORKSPACE\ai-toolkit\ui>npm run build_and_start

[email protected] build_and_start npm install && npm run update_db && npm run build && npm run start

up to date, audited 446 packages in 2s

61 packages are looking for funding run npm fund for details

5 vulnerabilities (1 low, 2 high, 2 critical)

To address issues that do not require attention, run: npm audit fix

To address all issues, run: npm audit fix --force

Run npm audit for details.

[email protected] update_db npx prisma generate && npx prisma db push

Prisma schema loaded from prisma\schema.prisma

✔ Generated Prisma Client (v6.3.1) to .\node_modules@prisma\client in 48ms

Start by importing your Prisma Client (See: https://pris.ly/d/importing-client)

Tip: Want to react to database changes in your app as they happen? Discover how with Pulse: https://pris.ly/tip-1-pulse

Prisma schema loaded from prisma\schema.prisma Datasource "db": SQLite database "aitk_db.db" at "file:../../aitk_db.db"

The database is already in sync with the Prisma schema.

✔ Generated Prisma Client (v6.3.1) to .\node_modules@prisma\client in 51ms

[email protected] build tsc -p tsconfig.worker.json && next build

▲ Next.js 15.1.7

Creating an optimized production build ... Failed to compile.

Error: EISDIR: illegal operation on a directory, readlink 'I:\WORKSPACE\ai-toolkit\ui\src\app\api\caption\get\route.ts'

Build failed because of webpack errors

(venv) I:\WORKSPACE\ai-toolkit\ui>

brazilgithub avatar Jul 21 '25 21:07 brazilgithub

Same Error all route.ts files wont load... So no Ai-Toolkit for me

Syscore64 avatar Jul 23 '25 19:07 Syscore64

This seems to be an issue if you try to run AI-Toolkit on Windows from a drive formatted in exFAT

FramnkRulez avatar Aug 15 '25 03:08 FramnkRulez

this worked for me: npm run dev

I kept getting that same error but this worked at least to open the webui, idk how training will go but fingers crossed

Image

youllneverguess avatar Dec 03 '25 18:12 youllneverguess

this worked for me: npm run dev

I kept getting that same error but this worked at least to open the webui, idk how training will go but fingers crossed

Image

Did it work for you?

zadokov avatar Dec 05 '25 12:12 zadokov