-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
express-serve-static-core
and serve-static
should be an explicit (optional) dependencies if their types are part of export
#4467
Comments
and
serve-static` should be an explicit (optional) dependencies if their types are part of exportexpress-serve-static-core
and serve-static
should be an explicit (optional) dependencies if their types are part of export
Adding # .yarnrc.yaml
packageExtensions:
# Missing dependencies that are part of types
webpack-dev-server@^4.9.0:
dependencies:
"@types/express-serve-static-core": '^4.17.18'
"@types/serve-static": '1.13.0' Gets me down to .yarn/__virtual__/webpack-dev-server-virtual-ca9edd4c98/2/.yarn/berry/cache/webpack-dev-server-npm-4.9.0-35850a5f47-8.zip/node_modules/webpack-dev-server/types/lib/Server.d.ts:3556:7 - error TS2315: Type 'ServeStaticOptions' is not generic.
3556 | import("serve-static").ServeStaticOptions<import("http").ServerResponse>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[9:47:52 AM] Found 1 error. Watching for file changes. edit: |
We don't use |
With #4468,
Is still failing. |
Just encountered. So, can |
Bug report
Actual Behavior
With Webpack-dev-server@4.9.0, typescript@4.7.2, and yarn@3.2.1
Expected Behavior
tsc should compile without error.
@types/express-serve-static-core
and@types/serve-static
should be an explicit (optional) dependencies if their types are part of export.How Do We Reproduce?
I'll try and create a repro repo later today.
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationThe text was updated successfully, but these errors were encountered: