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
I think that including a dependency on the Node.js typings isn't best practice, as then basically every library with typings on Npm would depend on that package, and instead it would be preferable if the end developers can add their own @types/node as a dev-dependency in their own projects.
This is currently causing us some issue when adding @valkey/valkey-glide (a native dependency that thus cannot be bundled) to our Lambda 😅
protobuf.js version: 7.3.3
@types/node
should be listed as adevDependency
. Here's the output of npmgraph showing the size of@types/node
:The text was updated successfully, but these errors were encountered: