This message was deleted.

Are you importing the modules A to module B? . I am doing that myself but with go without issues. I create resources 1,2,3 in package A and in package B I import the package A and use the resources 1,2,3 created on package A.

Hello Hernando and thanks for your answer... So if I take your example, I create the resources 1,2,3 in module A (app-services.ts) and export them there and in module B (key-vault.ts) I import the resources from module A. I can also access the resources from module A in module B, and for example I can also read the outputs from the resources 1,2,3 im module B. However, the dependencies I configured via "dependsOn" are not taken into account, that means the build order is not as I configured it via "dependsOn". If I now simply copy the code from module A into module B, then the build order works as configured in "dependsOn". I have therefore now placed the code for all resources in a single ts module - a bad solution that I actually did not want to have in this form.

Did you try passing the resources as arguments and handle empty resources?. Lets say in Package B you need to deploy an EC2 in a specific subnet but the subnet is created in Package A. Then your function/method on package B need to receive an argument that is the subnet from Package A. If the value is empty/null or whatever you dont want then handle that logic (i.e if len(subnet) < 1 {handle it here , dont create EC2 } else { continue creating the ec2}).