I'm not sure this is good advice.
I'm a fan of something called high cohesion and loose coupling. It's a concept where you strive for putting related code together and keeping modules as independent as possible.
When you put related code together and let the dependencies be obvious you usually get code that is easy to grasp. The advice in the article makes dependencies not so obvious... both for me and my tooling.
The advice in the article also make all components dependent on a global namespace which make them harder to share and remove.
Also... what happens when an updated version of Vue comes with a prototype property named like one of your dependencies. ...Boom?