How to unregister the extension?
See original GitHub issueI register the extension with:
cxtmenu(cytoscape)
But how to unregister?
Unregistering is needed in conjunction with Webpack’s hot module replacement.
If not unregistered the extension might get registered again while development, causing this error:
Can not register `cxtmenu` for `core` since `cxtmenu` already exists in the prototype and can not be overridden
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Unregister a Plug-In Package
Click Invoke Method to unregister the extension. Unregistering a plug-in package on vCenter Server does not delete the plug-in package files that are...
Read more >How to Uninstall Extensions in Chrome, Firefox, and Other ...
Click the “x” button to the right of an extension to remove it, or click the “Disable” button under an extension to disable...
Read more >How to delete or unregister vSphere Replication extension or ...
Under Methods, select void > UnregisterExtension. Click Invoke Method. You will see the message as “void“, which means its unregistered. Log in to...
Read more >How to unregister vCenter plugin/extension using the MOB
Select the specific plugin and then click on remove button. Here are the instructions to remove a specific plugin/extension from your vCenter ...
Read more >How to remove or uninstall Chrome extensions
How to uninstall an extension on Chrome · Open Chrome, and click / tap the menu button “…” · Click / tap More...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For me, the following worked:
Meanwhile I investigated it further and found I was wrong here:
Actually it’s due to my application, not Cytoscape, that the canvas is not rendered when hot replaced. Sorry for bothering you.
But still, Cytoscape reports the console message as an error, not as a warning which I can safely ignore. That gave me the (wrong) impression the problem is in Cytoscape.
Cytoscape should display that console message as a warning, not as an error. That would have avoided the entire misunderstanding in the first place.
And still I think an explicit
unregister
Core call is desired. This way theoverrideErr
could be prevented in the first place.Thank you for the support!