`wasp deps` command doesn't output the SDK deps

wasp-lang / wasp

The fastest way to develop full-stack web apps with React & Node.js.

https://wasp-lang.dev

MIT License

13.31k stars 1.18k forks source link

`wasp deps` command doesn't output the SDK deps #2227

Open infomiho opened 1 month ago

infomiho commented 1 month ago

We should decided if we want to keep this command, but if we do, we should make sure it outputs all the relevant deps. It now outputs the deps and dev deps used in the client and the server, but not the SDK.

Martinsos commented 1 month ago

Good catch! I believe the main motivation was to show these because users cared about them since they can come in conflict with their own deps. So, that is why they care about "framework code" deps. But for SDK code, they don't really need to know about the deps, as they don't have any contact with them. So it might be best if we stick to what we have, which is not showing them?