Can not find files when using concurrently

I have the following pipe:

"scripts": {
  "build": "concurrently -g npm:build:*",
  "build:generate-db": "ts-node ./converter/main.ts",
  "build:tailwind": "npx tailwindcss -i ./src/input.css -o ./static/css/build.css --minify",
  "build:hugo": "hugo --minify",
},

• build:generate-db: Create .md files for hugo application from a database.
• build:tailwind: Generates tailwind file and puts it in correct folder
• build:hugo: Creates hugo website with .md files and tailwind file.

When I run the script hugo is not finding the .md files. When I run the script a second time hugo finds the .md files and create the website correct.

When I try this config, it’s working:

"scripts": {
  "build": "concurrently -g npm:build:* & hugo --minify",
  "build:generate-db": "npm run converter",
  "build:tailwind": "npx tailwindcss -i ./src/input.css -o ./static/css/build.css --minify",
}

What I tried:

• First I thought the problem is the time the file write requires (so hugo is trying to find the files before they got written). This is not the case: Even when I sleep 10 seconds after build:generate-db hugo is not able to find the files as well.
• When I run build:generate-db and than build:hugo it’s working.
• The tailwind file is created correctly. (it’s also file write so why is this one working?)

The Converter writes like this:

writeFileSync(`${resultPath}/${data[titleKey]}.md`, JSON.stringify(resultDto, null, 2))

Here is the related stack overflow: https://stackoverflow.com/questions/71978982/hugo-can-not-find-created-files-by-node-when-using-concurrently

[paescuj]

I think the -g option does not really run the scripts sequentially, it just pretends to do so. From the docs:

  -g, --group           Order the output as if the commands were run
                        sequentially.

Why are you using concurrently for this? Since it seems like your scripts need to be run one after the other and in exact order…

[gustavohenke]

I’ll close this issue as it seems it’s a no-op for concurrently, but feel free to continue discussing!