The Problem

pdk makes a dependencies key in metadata.json no matter what. When given no dependencies it gives an empty array of dependencies.

This shouldn't matter but it does because of PUP-6964 and because of that ticket it means that users that run `pdk convert` on an existing module without a dependencies key might end up with a module that doesn't work anymore because it can't find functions from other modules ( most notably stdlib ).

Suggested Solution

We should omit the dependencies key when none are given.

Once PUP-6964 is resolved the original behavior can be restored.

Customer impact

Customers running `pdk convert` on an existing module with no dependencies may run into issues finding functions from other modules (most likely stdlib).