[BUG] after `dev-init` got `sh: mkdirp: command not found`

[soulteary]

trafficstars

Deployment details:

• App version 2.2.0
• Platform any
• Docker image tag 2.2.0

---

Bug description:

The current project lacks a development dependency, which leads to the problem of initialization failure when using the commands in the document.

npm run dev-init


> [email protected] dev-init
> npm run dir-init && npm run init-server && npm run init-client


> [email protected] dir-init
> npx mkdirp data public && touch public/flame.css public/customQueries.json

sh: mkdirp: command not found

When the dependency is completed, execute it again, and the problem is solved.

npm run dev-init       


> [email protected] dev-init
> npm run dir-init && npm run init-server && npm run init-client


> [email protected] dir-init
> npx mkdirp data public && touch public/flame.css public/customQueries.json


> [email protected] init-server
> echo Instaling server dependencies && npm install

Instaling server dependencies

---

In order to fix this problem, I submitted a pr https://github.com/pawelmalak/flame/pull/280

[Pezmc]

npx mkdirp shouldn't require mkdirp to be included in the project dependencies (see https://www.npmjs.com/package/npx), but I too can re-produce this. I wonder what's similar between our two development environments.