Not able to make Lightning Component work outside Managed Package Dev Org

After Spring '16 deployment the same component started working fine.

SFDC support was also not able to pin point the cause. They were able to reproduce it but have not suggested it as a bug (strange!).

Though Spring '16 deployment have magically fixed that. I'm now able to run my same old code without any modifications and no errors of internal server on tab load in managed packaged lightning component.

It seems I was in fact doing all things right.

Have you done anything as far as setting access so that your component (and any necessary resources it uses) are accessible outside of the package namespace?

I am not an expert at this, but when you build a package, and you need to make features (components, Apex classes, VF pages) accessible to the installing org to use, you must make them global. Perhaps this is your problem.

You have not mentioned setting access. So if you've not done this already, I would suggest having a read of the topic on setting access for lightning components. And then the topic on packaging and distributing components. This second has a link to the general ISV guide, which might help you check the other features are set as the correct access, too.

The syntax for doing this is trivial. On the open tag of any components you want the installing org to be able to use:

<aura:component access="global" ...all the other stuff... >