functions predeploy/postdeploy do not work when contains =

[aaharu]

[REQUIRED] Environment info

firebase-tools: 11.18.0

Platform: macOS

[REQUIRED] Test case

// firebase.json
{
  "functions": {
    "predeploy": "npm run build --workspace=packages/foobar",  // NG
    // "predeploy": "npm run build --workspace packages/foobar", // OK
    // "predeploy": "npm run build --workspace\\=packages/foobar", // OK
    // "predeploy": "npm run build -w packages/foobar", // OK
    // "predeploy": "npm --prefix \"$RESOURCE_DIR\" run build", // OK
    "source": "packages/foobar"
  }
}

$ firebase deploy --only functions

=== Deploying to '---'...

i  deploying functions
Running command: npm run build --workspace=packages/foobar
✔  functions: Finished running predeploy script.

It outputs Finished running predeploy script., but the predeploy was not running.
This behavior seems to be caused by cross-env-shell.

[REQUIRED] Steps to reproduce

Add predeploy script that contains = to firebase.json.

[REQUIRED] Expected behavior

The predeploy and postdeploy scripts have finished running.

[REQUIRED] Actual behavior

[google-oss-bot]

This issue does not have all the information required by the template. Looks like you forgot to fill out some sections. Please update the issue with more information.

[taeold]

@aaharu Thanks for bringing this to our attention. I wasn't aware of that limitation in cross-env package.

kentcdodds/cross-env#246

Looks like cross-env package is depreacted, and the work needed to fix this bug might amount to - "rewrite cross-env" :(. Frankly, that isn't something I can prioritize on, but if we see that many users are having similar problem we'll definitely revisit earlier.