toolchain.scaffold_read_failed

You ran jadpo new or jadpo package new on a path Jadpo can't look into, such as a folder you can't read or a path through a file.

Area 14, Tools; not declinable; the next step is usually the human's.

Why Jadpo refuses it

jadpo new writes only into a folder that doesn't exist yet or is empty, so before writing it looks at what is there. When it can't look, it can't tell whether writing would overwrite something, so it writes nothing and says why looking failed.

Jadpo won't change permissions or pick another path for you: both are decisions about your files.

What it looks like

notes is a file, and the path asks for a project inside it:

touch notesjadpo new notes/todo-app

(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: it decides where the project goes.

A folder you aren't allowed to read is refused the same way, with Permission denied as the reason.

How to fix it

If the path was a mistake, name a folder that doesn't exist yet, or an empty one:

jadpo new todo-app

Created todo-app    jadpo  X.Y    route  POST /hello    files  14 writtennext: cd todo-app && jadpo dev  serves it on http://localhost:3000

The project is in todo-app, and notes is untouched.

If the folder is one you aren't allowed to read, let yourself read it, then run the command again:

chmod u+rx todo-appjadpo new todo-app

jadpo new sees that the folder is empty and writes the project into it.

Related

• jadpo new
• The jadpo command