I came across this issue last week and alerted the internal packager team about it. We'll get it resolved- even if the issue is avoidable, we can help people avoid it with better tooling, errors, and documentation.