search

wcm-io-frontend / aem-clientlib-generator

Creates configuration files for AEM ClientLibs and synchronizes assets.
Apache License 2.0
62 stars 32 forks source link

Use of DOMNodeInserted Listener #56

Open mcst opened 4 weeks ago

mcst commented 4 weeks ago

Since Chrome Version 127.0.6533.100 (or earlier) the DOMNodeInserted listener is deprecated and no longer triggers an event.

The clientlib.min.js file generated by aem-clientlib-generator uses it and the project files are no longer available in the chrome sources:

document.body.addEventListener("DOMNodeInserted", (function() { return x(t) }

stefanseifert commented 4 weeks ago

are you sure aem-clientlib-generator is the source of this problem?

aem-clientlib-generator is only responsibly for transforming the source files generated by your project into a AEM-compatible clientlib format, but does not change or generate any additional logic in it.

creating the "min" version of the resulting library is done by the AEM HTML Library Manager (which may use -depending on your AEM version - quite outdated versions of the Google Closure Compiler - GCC).

mcst commented 4 weeks ago

Thank you very much for this information. We are using AEM as a Cloud Service and have AEM updated every two weeks.

The index.html has referenced the clientlib-loader...min.js file, which in turn should import the static files of the react app. The folder and the files that should be included are not available. How is this min.js file generated, because the only thing that happens on the client side is the call of the clientlib-generator. The files generated there are then copied to the web server. image