You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If so, then maybe webpack-dev-middleware needs to add @types/node@12 to its package.json. The phantom dependency is causing NPM to install the bleeding edge experimental version:
Bug report
Suppose a project is trying to maintain compatibility with Node 12 and/or 14:
webpack-dev-middleware
using TypeScript with@types/node
version 12.xActual Behavior
Expected Behavior
Node.js 12 is still LTS, so
webpack-dev-middleware
should be usable by projects that are trying to maintain support for Node 12 and/or 14.Suggested solution
The problem is here:
webpack-dev-middleware/types/index.d.ts
The
StatSyncFn
declaration was newly introduced in@types/node@16
:...whereas in
@types/node@14
and before, it looked like this:So the fix might look like this:
Is index.d.ts machine generated?
If so, then maybe
webpack-dev-middleware
needs to add@types/node@12
to its package.json. The phantom dependency is causing NPM to install the bleeding edge experimental version:webpack-dev-middleware/package-lock.json
Lines 3304 to 3308 in 4194cd0
The text was updated successfully, but these errors were encountered: