Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7 when trying to deploy functions

[sceee]

[REQUIRED] Environment info

firebase-tools: v12.2.1

Platform: Ubuntu (Github actions machine Ubuntu 22.04 with npm 9.5.1)

  node: v18.16.0
  npm: 9.5.1

[REQUIRED] Test case

N/A, this happens when trying to deploy functions that could previously be deployed without issues for a lot of times.
I have not seen this error before.

[REQUIRED] Steps to reproduce

Execute firebase deploy --project=default --only functions:myFunction

[REQUIRED] Expected behavior

Existing v1 Function is updated correctly.

[REQUIRED] Actual behavior

The following output is logged:

...
i  functions: updating Node.js 18 (1st Gen) function myFunction(europe-west3)...
Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7

Functions deploy had errors with the following functions:
      myFunction(europe-west3)
i  functions: cleaning up build files...
Error: There was an error deploying functions:
- Error Failed to update function myFunction in region europe-west3
Error: Process completed with exit code 2.

Unfortunately, I cannot find anything when searching for this error (id), it looks more like a Git hash to me.

[looptheloop88]

Hi @sceee, thanks for the report. I wasn't able to replicate the issue even though I've already used the same version of firebase-tools, npm and node.

I wrote and deployed a simple 1st Gen function, updated it then redeployed again. I didn’t encounter any issues or errors while deploying the function.

Are you seeing this error consistently? Would you mind sharing a sample code snippet of the 1st Gen function and the dependencies listed in your package.json file? Also, could you add --debug parameter in the deployment command you’re using and share the logs with us?

[richtu4n]

We also have this issue, nothing has changed in our code, everything worked before and as of today we're getting this same error.

Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7

[looptheloop88]

Just to confirm, are you trying to deploy the same function without any code changes? If so, did you see any message from the deployment logs indicating that that deployment of unchanged functions will be skipped?

[sceee]

@looptheloop88 it happened for both, functions with code change and functions without code changes (but dependency updates).

[looptheloop88]

@sceee thanks for the quick response. We need additional information from you to help us with the investigation. Please share the firebase-functions version that you're using or better if you could share the dependencies in the package.json file. Also, please try to get some logs by adding --debug parameter in the command you're using for deployment.

[inlined]

This error doesn't appear in the Firebase codebase, so it seems like there might be a tool that we depend on (e.g. npm) that is misconfigured. Can you provide your package.json? Feel free to redact anything sensitive such as dependencies or name.

[sceee]

Here are some parts of the package.json (name stripped, scripts stripped, some dependencies stripped):

{
  "name": "..........",
  "scripts": {
........
  },
  "engines": {
    "node": "18",
    "npm": "9"
  },
  "main": "lib/src/index.js",
  "dependencies": {
.......
    "firebase-admin": "^11.9.0",
    "firebase-functions": "^4.4.0",
.......
  },
  "devDependencies": {
    "@firebase/rules-unit-testing": "^2.0.7",
......
    "firebase": "^9.22.1",
    "firebase-functions-test": "^3.1.0",
.......
  },
  "private": true
}

@looptheloop88 firebase-functions is v4.4.0 (lockfile).

[richtu4n]

Not sure if this provides any more information, but this error detail comes before the error discussed above.

Here's our package.json

{
  "name": "firebase-functions",
  "version": "0.0.0",
  "main": "index.js",
  "private": true,
  "dependencies": {
    ...
    "firebase-admin": "^11.5.0",
    ...
    "firebase-functions": "^4.2.1",
    ...
  },
  "engines": {
    "node": "18",
    "npm": ">=8.0.0"
  }
}

firebase-functions: v4.4.0 (lockfile)
firebase-tools: v11.20.0 (locally)

[damorkas]

Started getting exact same error about ~20 hours ago.

Tried to update firebase-tools to the latest cause I see v12.3.0 showed up 5 hours ago but still same error.

[chrisfougner]

We're also seeing the same error, and are seeing it together with an error on too many concurrent builds:

Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7
Build failed: Too many concurrent builds, please stagger your deployments.

[hendrik244]

same problem here

[richtu4n]

Has anyone figured out a work around? We've completely lost our ability to deploy and rollback due to this issue 😵‍💫

[rvmoldova]

same here

functions: updating Node.js 18 (1st Gen) function *****(us-central1)...
Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7

Functions deploy had errors with the following functions:
        *****(us-central1)

[MehdiSaffar-Batelle]

I thought I was the only one with this error

...
Build failed: Too many concurrent builds, please stagger your deployments.
Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7
Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7
Build failed: Too many concurrent builds, please stagger your deployments.
Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7
Build failed: parsing npm version: Invalid Semantic Version; Error ID: f113d9b7
...

Is there a workaround? Using Node.js 18 with v1 functions

[albertjan]

Removing the npm version from the engines in package.json seems to fix the problem 🤷

[gboston]

Also seeing failing builds with cloud build. I've fixed it by pinning npm in the engines to 9.6.7. This prevents the new 9.7.0 to be used and apparently fixes the issue.

[mpsq]

Upstream bug: GoogleCloudPlatform/cloud-builders#922

The workaround is to update your package.json engine configuration to use a previous npm version:

"engines": {
  "npm": ">=9 <9.7"
}

[looptheloop88]

Thank you all for the inputs. I was able to replicate the issue now. The error occurs when semantic versioning syntax is used for the npm engine in the package.json file. Specifically, if the syntax is trying to use npm version 9.7.0.

"npm": "9" (failed)
"npm": ">=8.0.0" (failed)
"npm": "^9.6.7" (failed)
"npm": "~9.6.7" (successful)
"npm": "9.6.7" (successful)

The npm version 9.7.0 was released last 5/31/2023, but got deprecated. So the latest and active npm version is 9.6.7.

As for the workaround, remove npm under engines in package.json file or use semantic versioning syntax that will not use npm version 9.7.0.

[andredifs]

Thank you all for the inputs. I was able to replicate the issue now. The error occurs when semantic versioning syntax is used for the npm engine in the package.json file. Specifically, if the syntax is trying to use npm version 9.7.0.

"npm": "9" (failed) "npm": ">=8.0.0" (failed) "npm": "^9.6.7" (failed) "npm": "~9.6.7" (successful) "npm": "9.6.7" (successful)

The npm version 9.7.0 was released last 5/31/2023, but got deprecated. So the latest and active npm version is 9.6.7.

As for the workaround, remove npm under engines in package.json file or use semantic versioning syntax that will not use npm version 9.7.0.

It works for me:

"engines": {
    "node": "16",
    "npm": "~8.5.5", // before:  "npm": ">= 6.13.4",
    "yarn": ">= 1.21.1"
}

[AlexBeauchemin]

We can use semver's combining range to force the correct version until there's a new release
This worked for us

  "engines": {
    "node": "18",
    "npm": ">=9.5 <9.7"
  },

[aalej]

Hey everyone! Per checking, it looks like a new version of npm was released, v9.7.1. I’ve tried out the following configurations and all seems to work properly:

"npm": ">=9"
"npm": "9"
"npm": "^9.6.7"

With that being said, I’m going to close this issue. If anyone thinks this may be a mistake, feel free to ask this issue to be reopened. Thanks!