v3.4.3 upgraded to `@types/express:^5.0.0` although `express:^4.21.2` is used

[caugner]

In 16709c6, @matthewrobertson bumped @types/express from 4.17.21 to ^5.0.0, which probably wasn't intended.

This causes issues, because the RouteParameters type in @types/express-serve-static-core, which is used by @types/express, changed slightly between v4 and v5

This caused unexpected issues for us when upgrading dependencies in https://github.com/mdn/yari/blob/main/cloud-function/package.json, as @sentry/google-cloud-serverless 8.54.0 expects express v4 types.

[zymotik]

This is also causing issues because of incompatibilities with the Google Cloud Identity Platform Blocking Functions if used with @google-cloud/functions-framework.

In addition to what @caugner mentions above, my question is: Are types really a dependency? Should they not be moved to devDependencies?

If this helps anyone else with type issues while building their cloud functions, I've added an override to my package.json temporarily so that I can build my project without mismatched type failures:

{
  ...
  "overrides": {
    "@types/express": "^4.0.0"
  }
}

[zymotik]

You may need to use v5 here instead.

If this helps anyone else with type issues while building their cloud functions, I've added an override to my package.json temporarily so that I can build my project without mismatched type failures:

{
...
"overrides": {
"@types/express": "^4.0.0"
}
}