Recently i noticed, that Jon wants to deprecate a module (he moved it to another location and changed the module name)[1], so I thought about a better way of deprecating a module (like core functions with a visible deprecation warning in the browser console, e.g.). So I uploaded a change for review[2] to extend module.js to support the definition of a deprecated module (it will log a warning every time someone access the module with M.require). Jon already posted, that he don’t know, if this is the right approach and suggested to extend core’s mw.log.deprecate. I’m not sure, if it’s a better approach to extend a core module in this way, so I hope for some feedback on this mailing list: What do you think? :)

[1] https://gerrit.wikimedia.org/r/#/c/202053/3/javascripts/ContentOverlay.js

[2] https://gerrit.wikimedia.org/r/#/c/202069/

Best,

Florian