OOTB Console errors in 6.5 Upgraded Page | Community
Skip to main content
akhilraj
Level 5
April 14, 2022
Solved

OOTB Console errors in 6.5 Upgraded Page

  • April 14, 2022
  • 3 replies
  • 1014 views

Hi Team,

 

We are getting below errors in few of our pages but pages are functioning properly. This errors are coming for 6.5 upgraded instances only in few pages. rest of the pages are looking neat in console.

As it is OOTB errors, not sure what to do.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by DEBAL_DAS

It might be clientlib dependency is causing this issue.

 

We can refer below steps to troubleshoot the issue -

1. As you are facing the said issue with few pages, were those page created with same template?

   if yes, then please check page rendering component via sling:resourceType property at jcr:content node  

   of page.

   Check what are the clientlibaries are getting used , dependency client libraries like below one -

 

and compare with dependency client libraries associated with pages where you aren't seeing this issue.

 

2. Regarding babel-polyfill  issue please refer below links -

 

https://stackoverflow.com/questions/53287691/uncaught-error-only-one-instance-of-babel-polyfill-is-allowed-error-on-producti

https://github.com/babel/babel-loader/issues/401

https://stackoverflow.com/questions/43902416/only-one-instance-of-babel-polyfill-is-allowed-error

 

3 replies

Ritesh_Mittal
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
April 14, 2022

Hi @akhilraj ,

 

Looks like babel-polyfill has been included multiple times (third party libraries?), can you check your web-config. Just check below thread-

 

https://lifesaver.codes/answer/babel-polyfill-error-error-only-one-instance-of-babel-polyfill-is-allowed-401 

DEBAL_DAS
DEBAL_DASAccepted solution
New Member
April 14, 2022

It might be clientlib dependency is causing this issue.

 

We can refer below steps to troubleshoot the issue -

1. As you are facing the said issue with few pages, were those page created with same template?

   if yes, then please check page rendering component via sling:resourceType property at jcr:content node  

   of page.

   Check what are the clientlibaries are getting used , dependency client libraries like below one -

 

and compare with dependency client libraries associated with pages where you aren't seeing this issue.

 

2. Regarding babel-polyfill  issue please refer below links -

 

https://stackoverflow.com/questions/53287691/uncaught-error-only-one-instance-of-babel-polyfill-is-allowed-error-on-producti

https://github.com/babel/babel-loader/issues/401

https://stackoverflow.com/questions/43902416/only-one-instance-of-babel-polyfill-is-allowed-error

 

Debal Das, Senior AEM Consultant
akhilraj
akhilrajAuthor
Level 5
July 11, 2022

The inclusion of coralui3 fixed the issue. Thank you all