Why aren't dependencies exported alongside a flow.json?
Someone shared with me his flow.json but he forgot to tell me the dependencies. Now I can't run his flow unless I know the package dependencies.
Unfortunately, the dependencies are separate to the flow and are stored in the package.json. It would not be safe to share that file. Though not a bad enhancement request for node-red maybe to at least show the dependencies when you export?
There is, however, a rather well hidden web page that will show you what dependencies a flow file has. Paste the flow into there and it should tell you:
3 Likes
Because the flow JSON is an array and until recently had no means of including meta data. Oh, and the fact it was not designed like that from the outset.
There is a thread (or 10) that discusses flow file format improvements that could (should) hit this very matter (would take me some digging to find)
1 Like
This 
3 Likes
