[@types/express] Namespace 'serveStatic' has no exported member 'RequestHandlerConstructor'

[SunSeekerX]

No description provided.

[SunSeekerX]

[sk-]

It's a problem with the type dependencies for the express types. See #47339.

These commands fixed it for me:

npm update @types/express-serve-static-core --depth 2
npm update @types/serve-static --depth 2

[SunSeekerX]

It's a problem with the type dependencies for the express types. See #47339.

These commands fixed it for me:

npm update @types/express-serve-static-core --depth 2
npm update @types/serve-static --depth 2

Thank you,but i remove the @types/express dependence in my dependencies.
It works for me,my project base on nestjs, it seems does't need this dependence.

[adamgarcia4]

Also having this issue. +1

[ignlg]

Removing the @types/express dependency fixed the issue in a API project based on Express (without NestJS). Upgrading server-static typing dependencies did not work in my case.

[goalia]

+1 when I installed twilio API with NestJS

[hrahimi270]

This helped me as a temp solution:
yarn add @types/express@4.17.8

[jonsadka]

Removing the @types/express dependency fixed the issue in a API project based on Express (without NestJS)

Same for me

[DmytroA]

+1 when I installed twilio API with NestJS

@Benjamin-Gardien were you able to solve problem with Twilio api?

[goalia]

@DmytroA it's my teammate @QuanticPotatoes who solved this issue 👌🏼

[yannickschuchmann]

I'm in a firebase project so for me the issue was with firebase-functions.
It uses fixed version of @types/express@4.17.3.

Since 4.17.9 is backwards compatible (fortunately 😄) I've set the resolution for all express types to 4.17.9. And that solved it for me. 🎉

// package.json
{
  "dependencies": {
    "@types/express": "4.17.9"
  // ...
  },
  "resolutions": {
    "@types/express": "4.17.9"
  }
}

[deividr]

It's a problem with the type dependencies for the express types. See #47339.

These commands fixed it for me:

npm update @types/express-serve-static-core --depth 2
npm update @types/serve-static --depth 2

Its works for me... Thanks!!!

[maiconmichelon]

It's a problem with the type dependencies for the express types. See #47339.

These commands fixed it for me:

npm update @types/express-serve-static-core --depth 2
npm update @types/serve-static --depth 2

I use yarn, then I removed those dependencies from yarn.lock and installed again and It worked for me, thanks!

[exsesx]

It's a problem with the type dependencies for the express types. See #47339.
These commands fixed it for me:

npm update @types/express-serve-static-core --depth 2
npm update @types/serve-static --depth 2

I use yarn, then I removed those dependencies from yarn.lock and installed again and It worked for me, thanks!

This works for me now too, thanks.

[phattranky]

It's a problem with the type dependencies for the express types. See #47339.
These commands fixed it for me:

npm update @types/express-serve-static-core --depth 2
npm update @types/serve-static --depth 2

Thank you,but i remove the @types/express dependence in my dependencies.
It works for me,my project base on nestjs, it seems does't need this dependence.

Works for me as well. I'm using NestJS

[andrerpena]

Literally removing "@types/express": "^4.17.11", from my package.json did the trick.

[VincentDebug]

"@types/express": "4.17.11",
"@types/express-serve-static-core": "4.17.19",
"@types/serve-static": "1.13.9",

Add these to package.json, this helped me as a temp solution.

[cprodescu]

If you are having conflicts due to multiple libraries pulling in @types/express (in my case: probot, apollo-server-express), you can get away with using a resolution just for @types/serve-static:

"resolutions": {
  "@types/serve-static": "1.13.9"
}

[fastfedora]

If you are having conflicts due to multiple libraries pulling in @types/express (in my case: probot, apollo-server-express), you can get away with using a resolution just for @types/serve-static:

"resolutions": {
  "@types/serve-static": "1.13.9"
}

This worked for me for firebase-functions when fixing the resolution for @types/express didn't work.

[Koslun]

Setting resolution to "@types/serve-static": "1.13.9" fixed it for me as well after trying a lot of other stuff.

A more permanent fix would be for @types/express to rely on "@types/serve-static": "> 1.13.9" instead of "@types/serve-static": "*" . That it relies on "*" is the reason fresh installs may work but plenty of random updates don't.

[viktorzavadil]

This helped me as a temp solution: yarn add @types/express@4.17.8

For me version 4.17.13 has same troubles.

[Yogu]

The pull request created by @RMacfarlane triggered a test that basically said "these versions should not be specified"

Error: In package.json: Dependency @types/serve-static not in the allowed dependencies list.
Don't use a 'package.json' for @types dependencies unless this package relies on
an old version of types that have since been moved to the source repo.
For example, if package P used to have types on Definitely Typed at @types/P,
but now has its own types, a dependent package D will need to use package.json
to refer to @types/P if it relies on old versions of P's types.
In this case, please make a pull request to microsoft/DefinitelyTyped-tools adding @types/P to packages/definitions-> parser/allowedPackageJsonDependencies.txt.

The messages does not explain why this should not be done, and I can't find the source for this message.

There is an issue that explains the problem with specifying everything as "*" that also suggest to lift this restriction, but there has been no response since October 2019.

How can this be fixed then?

[sangimed]

It's a problem with the type dependencies for the express types. See #47339.

These commands fixed it for me:

npm update @types/express-serve-static-core --depth 2
npm update @types/serve-static --depth 2

it does solve the issue 😃

[connorads]

yarn user here - just deleted yarn.lock file and did yarn install again and it's working
connorads/lockbot#174

[DanielLMA]

yarn user here - just deleted yarn.lock file and did yarn install again and it's working connorads/lockbot#174

"express": "^4.17.1",
"@types/express": "^4.17.2",

deleted my package.lock.json and fresh npm i and no longer had this error

[ruscon]

It's a problem with the type dependencies for the express types. See #47339.

These commands fixed it for me:

npm update @types/express-serve-static-core --depth 2
npm update @types/serve-static --depth 2

works

I have

"express": "^4.18.2",
"express-correlation-id": "^2.0.1",

"@types/express": "^4.17.21",
"@types/express-correlation-id": "^1.2.4",
"@types/express-serve-static-core": "^4.17.43",
"@types/serve-static": "^1.15.5"