Do not cache libraries when playing a plugin from the Plugin Creator console

When working on plugins involving external javascript libraries, it is not uncommon to modify those libraries during the development process and to expect the next run of the plugin to use the updated versions of the libraries.

(In this example, the plugin is using a piece of javascript defined in a "testlib.js" file.)

However, MS seems to load those libraries the first time they are required and to cache them. While this is understandable in the MS front-end, this is not convenient in the Plugin Creator console.

In this case, the modifications brought to the testlib.js are not taken into account, unless one goes to the MS frontend and ask for reloading the plugins.

This request is to have either:

• (As I user) I want that every time I run a plugin from the Plugin Creator console, the imported libraries are re-read from their source location automatically instead of being read from cache, in order to take into account the modifications brought to those libraries.

-or-

• (As I user) I want to have a toolbar button in the Plugin Creator console that would clean the cache of libraries in order that, at the next run of the plugin in the console, the libraries will be re-read from their source location and the modifications brought to the libraries taken into account.