You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had built a custom module based on oj3 which now I have migrated to oj5 and I am trying to consume this in another module (also using oj5). However, when I try to load the page, it gives below error:- Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': this name has already been used with this registry at Object../node_modules/@oracle/oraclejet/dist/js/libs/oj/debug/ojcomponentcore.js.oj.CustomElementBridge.register
On looking further, I found that a certain 'oj-surrogate' is being registered in ojpopupcore.js (line: 1988) like this:- oj.CustomElementBridge.register('oj-surrogate', {'metadata' : oj.CustomElementBridge.getMetadata('oj-surrogate')});
which is throwing this exception.
I am not sure if it is because of overlapping libraries between the built bundles of the component and the consumer.
Note:- This issue did not occur in previous version of OJ. It only came up after upgrading to OJ5.
The text was updated successfully, but these errors were encountered:
I had built a custom module based on oj3 which now I have migrated to oj5 and I am trying to consume this in another module (also using oj5). However, when I try to load the page, it gives below error:-
Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': this name has already been used with this registry at Object../node_modules/@oracle/oraclejet/dist/js/libs/oj/debug/ojcomponentcore.js.oj.CustomElementBridge.register
On looking further, I found that a certain 'oj-surrogate' is being registered in ojpopupcore.js (line: 1988) like this:-
oj.CustomElementBridge.register('oj-surrogate', {'metadata' : oj.CustomElementBridge.getMetadata('oj-surrogate')});
which is throwing this exception.
I am not sure if it is because of overlapping libraries between the built bundles of the component and the consumer.
Note:- This issue did not occur in previous version of OJ. It only came up after upgrading to OJ5.
The text was updated successfully, but these errors were encountered: