toolchain.scaffold_destination_not_empty

You ran jadpo new or jadpo package new on a folder that already has files in it, hidden files included.

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

Why Jadpo refuses it

jadpo new <name> writes a whole project: app.jadpo, a first route, its records and the rest. Writing it into a folder that holds anything could overwrite your files or mix them with the new project's, so it writes only into a folder that doesn't exist yet or is empty. A hidden file, such as .git or .env.local, counts. It refuses and changes nothing.

Jadpo won't pick another folder or empty this one for you: a new name gives you a second project, and emptying the folder deletes what was in it.

What it looks like

A folder todo-app already holds a hidden file:

mkdir todo-apptouch todo-app/.gitignorejadpo new 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 whether the files already in todo-app are kept.

How to fix it

If the files in the folder should stay, name a folder that doesn't exist yet:

jadpo new todo-app-2

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

The new project is in todo-app-2, and todo-app is untouched.

If they can go, empty todo-app yourself, hidden files included, then run the command again:

jadpo new todo-app

The project is written into todo-app.

Related

• jadpo new
• The jadpo command