diff --git a/css/jquery.contextMenu.css b/css/jquery.contextMenu.css
index ee58116f4..fc09965f1 100755
--- a/css/jquery.contextMenu.css
+++ b/css/jquery.contextMenu.css
@@ -1,3 +1,7 @@
+/**
+ * @deprecated 3.2.0 N°5621 Moved to NPM
+ */
+
/*!
* jQuery contextMenu - Plugin for simple contextMenu handling
*
diff --git a/js/jquery.contextMenu.js b/js/jquery.contextMenu.js
index 103a58582..bdfd534ed 100755
--- a/js/jquery.contextMenu.js
+++ b/js/jquery.contextMenu.js
@@ -1,3 +1,7 @@
+/**
+ * @deprecated 3.2.0 N°5621 Moved to NPM
+ */
+
/*!
* jQuery contextMenu - Plugin for simple contextMenu handling
*
diff --git a/node_modules/.package-lock.json b/node_modules/.package-lock.json
index 97ba31847..6bd5e0b24 100644
--- a/node_modules/.package-lock.json
+++ b/node_modules/.package-lock.json
@@ -111,6 +111,14 @@
"resolved": "https://registry.npmjs.org/jquery/-/jquery-3.5.1.tgz",
"integrity": "sha512-XwIBPqcMn57FxfT+Go5pzySnm4KWkT1Tv7gjrpT1srtf8Weynl6R273VJ5GjkRb51IzMp5nbaPjJXMWeju2MKg=="
},
+ "node_modules/jquery-contextmenu": {
+ "version": "1.6.7",
+ "resolved": "https://registry.npmjs.org/jquery-contextmenu/-/jquery-contextmenu-1.6.7.tgz",
+ "integrity": "sha512-6qPEpiquUCE3iMbChPOHReQSKRus8VdPoDrJJMRYHBKSj577cAllLqMfp2pBzxax6m2ASTSt+YY++DWxt5yxGA==",
+ "dependencies": {
+ "jquery": ">=1.7.0"
+ }
+ },
"node_modules/jquery-ui-dist": {
"version": "1.12.1",
"resolved": "https://registry.npmjs.org/jquery-ui-dist/-/jquery-ui-dist-1.12.1.tgz",
diff --git a/node_modules/jquery-contextmenu/README.md b/node_modules/jquery-contextmenu/README.md
new file mode 100644
index 000000000..0b86855b7
--- /dev/null
+++ b/node_modules/jquery-contextmenu/README.md
@@ -0,0 +1,339 @@
+# jQuery contextMenu plugin & polyfill #
+
+---
+
+> [**This repository is looking for a new maintainer**](https://github.com/medialize/jQuery-contextMenu/issues/257)
+
+---
+
+[](https://travis-ci.org/medialize/jQuery-contextMenu)
+
+$.contextMenu is a management facility for - you guessed it - context menus. It was designed for an application where there are hundreds of elements that may show a context menu - so intialization speed and memory usage are kept fairly small. It also allows to register context menus without providing actual markup, as $.contextMenu generates DOMElements as needed.
+
+[features](http://medialize.github.com/jQuery-contextMenu/index.html) -
+[demo](http://medialize.github.com/jQuery-contextMenu/demo.html) -
+[documentation](http://medialize.github.com/jQuery-contextMenu/docs.html)
+
+
+## Dependencies ##
+
+* jQuery 1.7 (using new .on().off() event API)
+* jQuery UI position (optional but recommended)
+
+## Usage ##
+
+register contextMenu from javascript:
+
+```javascript
+$.contextMenu({
+ // define which elements trigger this menu
+ selector: ".with-cool-menu",
+ // define the elements of the menu
+ items: {
+ foo: {name: "Foo", callback: function(key, opt){ alert("Foo!"); }},
+ bar: {name: "Bar", callback: function(key, opt){ alert("Bar!") }}
+ }
+ // there's more, have a look at the demos and docs...
+});
+```
+
+have a look at the [demos](http://medialize.github.com/jQuery-contextMenu/demo.html).
+
+
+## HTML5 Compatibility ##
+
+Firefox 8 implemented contextmenu using the <menuitem> tags for menu-structure. The specs however state that <command> tags should be used for this purpose. $.contextMenu accepts both.
+
+Firefox 8 does not yet fully implement the contextmenu specification ([Ticket #617528](https://bugzilla.mozilla.org/show_bug.cgi?id=617528)). The elements
+[a](http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#using-the-a-element-to-define-a-command),
+[button](http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#using-the-button-element-to-define-a-command),
+[input](http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#using-the-input-element-to-define-a-command) and
+[option](http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#using-the-option-element-to-define-a-command)
+usable as commands are being ignored altogether. It also doesn't (optically) distinguish between checkbox/radio and regular commands ([Bug #705292](https://bugzilla.mozilla.org/show_bug.cgi?id=705292)).
+
+* [contextmenu specs](http://www.w3.org/TR/html5/interactive-elements.html#context-menus)
+* [command specs](http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html)
+* [Browser support according to caniuse.com](http://caniuse.com/#search=context%20menu)
+
+Note: While the specs note <option>s to be renderd as regular commands, $.contextMenu will render an actual <select>. import contextMenu from HTML5 <menu>:
+
+```javascript
+$.contextMenu("html5");
+```
+
+## Interaction Principles ##
+
+You're (obviously) able to use the context menu with your mouse. Once it is opened, you can also use the keyboard to (fully) navigate it.
+
+* ↑ (up) previous item in list, will skip disabled elements and wrap around
+* ↓ (down) next item in, will skip disabled elements and wrap around
+* → (right) dive into sub-menu
+* ← (left) rise from sub-menu
+* ↵ (return) invoke command
+* ⇥ (tab) next item or input element, will skip disabled elements and wrap around
+* ⇪ ⇥ (shift tab) previous item or input element, will skip disabled elements and wrap around
+* ⎋ (escape) close menu
+* ⌴ (space) captured and ignore to avoid page scrolling (for consistency with native menus)
+* ⇞ (page up) captured and ignore to avoid page scrolling (for consistency with native menus)
+* ⇟ (page down) captured and ignore to avoid page scrolling (for consistency with native menus)
+* ↖ (home) first item in list, will skip disabled elements
+* ↘ (end) last item in list, will skip disabled elements
+
+Besides the obvious, browser also react to alphanumeric key strokes. Hitting r in a context menu will make Firefox (8) reload the page immediately. Chrome selects the option to see infos on the page, Safari selects the option to print the document. Awesome, right? Until trying the same on Windows I did not realize that the browsers were using the access-key for this. I would've preferred typing the first character of something, say "s" for "save" and then iterate through all the commands beginning with s. But that's me - what do I know about UX? Anyways, $.contextMenu now also supports accesskey handling.
+
+
+## Minify ##
+
+use [Google Closure Compiler](http://closure-compiler.appspot.com/home):
+
+```
+// ==ClosureCompiler==
+// @compilation_level SIMPLE_OPTIMIZATIONS
+// @output_file_name contextMenu.js
+// @code_url http://medialize.github.com/jQuery-contextMenu/jquery-1.8.2.min.js
+// @code_url http://medialize.github.com/jQuery-contextMenu/src/jquery.ui.position.js
+// @code_url http://medialize.github.com/jQuery-contextMenu/src/jquery.contextMenu.js
+// ==/ClosureCompiler==
+```
+
+
+## Authors ##
+
+* [Rodney Rehm](https://github.com/rodneyrehm)
+* [Christiaan Baartse](https://github.com/christiaan) (single callback per menu)
+* [Addy Osmani](https://github.com/addyosmani) (compatibility with native context menu in Firefox 8)
+
+
+## License ##
+
+$.contextMenu is published under the [MIT license](http://www.opensource.org/licenses/mit-license) or [GPL v3](http://opensource.org/licenses/GPL-3.0) - which ever suits your needs best.
+
+
+## Changelog ##
+
+### 1.6.7 (May 21st 2015) ###
+
+* looking for maintainer note
+* publish to npm
+
+### 1.6.6 (July 12th 2014) ###
+
+* fixing bower manifest
+
+### 1.6.5 (January 20th 2013) ###
+
+* fixing "opening a second menu can break the layer" - ([Issue #105](https://github.com/medialize/jQuery-contextMenu/issues/105))
+
+### 1.6.4 (January 19th 2013) ###
+
+* fixing [jQuery plugin manifest](https://github.com/medialize/jQuery-contextMenu/commit/413b1ecaba0aeb4e50f97cee35f7c367435e7830#commitcomment-2465216), again. yep. I'm that kind of a guy. :(
+
+### 1.6.3 (January 19th 2013) ###
+
+* fixing [jQuery plugin manifest](https://github.com/medialize/jQuery-contextMenu/commit/413b1ecaba0aeb4e50f97cee35f7c367435e7830#commitcomment-2465216)
+
+### 1.6.2 (January 19th 2013) ###
+
+* fixing "menu won't close" regression introduced by 1.6.1
+
+### 1.6.1 (January 19th 2013) ###
+
+* fixing potential html parsing problem
+* upgrading to jQuery UI position v1.10.0
+* replaced `CRLF` by `LF` (no idea how this happened in the first place...)
+* adding `options.reposition` to dis/allow simply relocating a menu instead of rebuilding it ([Issue #104](https://github.com/medialize/jQuery-contextMenu/issues/104))
+
+### 1.6.0 (December 29th 2012) ###
+
+* adding [DOM Element bound context menus](http://medialize.github.com/jQuery-contextMenu/demo/on-dom-element.html) - ([Issue 88](https://github.com/medialize/jQuery-contextMenu/issues/88))
+* adding class `context-menu-active` to define state on active trigger element - ([Issue 92](https://github.com/medialize/jQuery-contextMenu/issues/92))
+* adding [demo for TouchSwipe](http://medialize.github.com/jQuery-contextMenu/demo/trigger-swipe.html) activation
+* adding export of internal functions and event handlers - ([Issue 101](https://github.com/medialize/jQuery-contextMenu/issues/101))
+* fixing key "watch" might translate to Object.prototype.watch in callbacks map - ([Issue 93](https://github.com/medialize/jQuery-contextMenu/issues/93))
+* fixing menu and submenu width calculation - ([Issue 18](https://github.com/medialize/jQuery-contextMenu/issues/18))
+* fixing unused variables - ([Issue 100](https://github.com/medialize/jQuery-contextMenu/issues/100))
+* fixing iOS "click" compatibility problem - ([Issue 83](https://github.com/medialize/jQuery-contextMenu/issues/83))
+* fixing separators to not be clickable - ([Issue 85](https://github.com/medialize/jQuery-contextMenu/issues/85))
+* fixing issues with fixed positioned triggers ([Issue 95](https://github.com/medialize/jQuery-contextMenu/issues/95))
+* fixing word break problem - ([Issue 80](https://github.com/medialize/jQuery-contextMenu/issues/80))
+
+### 1.5.25 (October 8th 2012) ###
+
+* upgrading to jQuery 1.8.2 ([Issue 78](https://github.com/medialize/jQuery-contextMenu/issues/78))
+* upgrading to jQuery UI position 1.9.0 RC1 ([Issue 78](https://github.com/medialize/jQuery-contextMenu/issues/78))
+
+### 1.5.24 (August 30th 2012) ###
+
+* adding context menu options to input command events ([Issue 72](https://github.com/medialize/jQuery-contextMenu/issues/72), dtex)
+* code cosmetics for JSLint
+
+### 1.5.23 (August 22nd 2012) ###
+
+* fixing reposition/close issue on scrolled documents ([Issue 69](https://github.com/medialize/jQuery-contextMenu/issues/69))
+* fixing jQuery reference ([Issue 68](https://github.com/medialize/jQuery-contextMenu/issues/68))
+
+### 1.5.22 (July 16th 2012) ###
+
+* fixing issue with animation and remove on hide (Issue #64)
+
+### 1.5.21 (July 14th 2012) ###
+
+* fixing backdrop would not remove on destroy (Issue #63)
+
+### 1.5.20 (June 26th 2012) ###
+
+Note: git tag of version is `v1.6.20`?!
+
+* fixing backdrop would not position properly in IE6 (Issue #59)
+* fixing nested input elements not accessible in Chrome / Safari (Issue #58)
+
+### 1.5.19 ###
+
+Note: git tag of version is missing...?!
+
+* fixing sub-menu positioning when `$.ui.position` is not available (Issue #56)
+
+### 1.5.18 ###
+
+Note: git tag of version is missing...?!
+
+* fixing html5 `