[BUG] BREAKING REGRESSION npm concurrency regression in 4.1.0 and onwards

[jlarmstrongiv]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When running NPM scripts concurrently, some will fail with errors like:

• /tmp/ *** .sh: Text file busy
• Error: ETXTBSY: text file is busy, open '/tmp/ *** .sh'

Expected Behavior

NPM scripts run as expected when run concurrently by using unique filenames.

The current implementation is:

const fileName = escape.filename(`${event}-${Date.now()}`)

Unfortunately, when two scripts run at the same time with the same filename due to Date.now(), NPM will error. Instead, files should be named uniquely. In the NPM cli, this implementation avoids the error:

const rand = require('crypto').randomBytes(4).toString('hex')

Steps To Reproduce

1. With the latest version of NPM
2. Run two NPM scripts at the exact same second
3. Log error

Environment

• npm: 8.13.2
• Node: v16.15.0
• OS: Ubuntu 20.04
• platform: GitHub Actions

[jlarmstrongiv]

Last working NPM version according to #90 is 8.12.2