...not during publish. During publish we can end up verifying a to-be-published module's dependencies without them being loaded if they exist in the same bundle that is currently being published.
In that case, we don't want to mark the module as having its dependencies verified because that will prevent us from traversing (and actually loading into the compiled module cache) the dependencies when we are loading the module itself.
This manifests as a MISSING_DEPENDENCY error from the loader.
Test Plan
New tests for the loader, exercising the bundle publish flow:
...not during
publish. Duringpublishwe can end up verifying a to-be-published module's dependencies without them being loaded if they exist in the same bundle that is currently being published.In that case, we don't want to mark the module as having its dependencies verified because that will prevent us from traversing (and actually loading into the compiled module cache) the dependencies when we are loading the module itself.
This manifests as a
MISSING_DEPENDENCYerror from the loader.Test Plan
New tests for the loader, exercising the bundle publish flow: