extend plugmatic to upgrade core javascript as well as plugins

[WardCunningham]

The plugin ignores markup that is not a keyword or plugin name that matches wiki-plugin-*.

Even if the client is generalized to accept core component names, the server site is nowhere near ready to even receive these names let alone query or command npm to do anything with them.

The client and server both assume a defensive posture of plugins-only which will take some effort to redesign. One experiment would be to special case client and server to confirm that these modules can be dynamically substituted without adverse effects. Then an appropriately defensive logic than be crafted to take this into account.

Opinions @paul90?

[paul90]

I'm really not sure. Such a move would certainly need some defensive logic - to ensure the wiki was not left inaccessible.

Generally new server and to some extent client versions, especially where the minor version has been incremented, are an indication that something major has been updated, may require updates to both and possible updates to existing plugins or additional ones may be required.

Some of updates may also require an update to the wiki version - if only to pickup additional configuration for use in other components.