unexpected token: identifier

Complementary information :
The issue is encountered on Firefox, Brave, Chrome and Edge but not Opera

You need LiteSpeed web server to benefit of all features of the cache plugin, so disable the cache or use quic.cloud to benfit of all features if Apache web server is used.

• This reply was modified 1 year ago by mukoka.

please try disable all the JS options purge all , see how it goes

@mukoka we are using LiteSpeed Cache like this in 6 website. This is the only one to encounter this issue ; we ask to solve it.

Hello @qtwrk ; can you explain how to do this/these steps ?

I’m not sure if you ask for “disable all the JS options” and “purge all” (I already did this second part, on -ALL-, -css/js only- or even -totally- many times ; it is a part of my plugins upgrade routine), or if it is a global operation unknown from me.

@omasmulticam

The LiteSpeed cache plugin needs LiteSpeed webserver to use all features, especially the cache function! The link you provided in the first post refers to a host that is using Apache web server, so if you have any trouble with some functions for optimization this is caused by missing the correct web server.

I was referring to Page Optm -> JS options , turn off all them

@qtwrk

I went into LiteSpeed Cache > Page Optimisation > [2] JS Settings and updated :

• Minifier JS from ENABLED to DISABLED
• Charger le JS en différé (Differed JS Loading ?) from DIFFERED to DISABLED

The issue seems to be solved. Thank you.

But I understand these JS optimisations are now inefficient…

What is your diagnoses ?

now enable only one of them back , see what it shows

I updated :

1. Charger le JS en différé?(Differed JS Loading ?) from DISABLED to DIFFERED : OK, it still working
2. Minifier JS?from DISABLED to ENABLED : KO, the issue re-appears

I repeated the second step many time (2 or 3) to be sure : the issue reappears each time I pute Minifier JS to ENABLED.

okay , then please check this page

Following your page, I listed and added all the files to excluded js files.

Unfortunately the issue still occurs. But something is weird : there is always 3 files which seems to be handled by Litespeed cache :

https://dev.multicam-location.com/product/pupitre-commentateur-rami-prt-900-2-micro-casques/

2024-03-21 12_15_30-PUPITRE COMMENTATEUR RAMI PRT 900 + 2 MICRO-CASQUES – multiCAM Location — Mozill.png

By the way, I discovered the prod version of my website is using .min.js files, whereas the dev one does not. Maybe there is something else :

• https://www.multicam-location.com/product/decimator-md-hxhdmi-sdi-cross-converter-et-scaler/?LSCWP_CTRL=before_optm
  Example : woocommerce.min.js?ver=8.6.1
• https://dev.multicam-location.com/product/pupitre-commentateur-rami-prt-900-2-micro-casques/?LSCWP_CTRL=before_optm
  Example : woocommerce.js

I will do another check up further, maybe I missed something.

After a fascinating experience, voilà :

• elementor/assets/js/frontend.js
• elementor-pro/assets/js/frontend.js
• elementor/assets/js/frontend-modules.js
• elementor/assets/js/webpack.runtime.js

Now these files are excluded from minification process, so our dev environnement is now working.

Can you explain why these files aren’t correctly minified by Litespeed Cache plugin ? Will there be a patch to handle these ones ?

The issue appears apparently after a 19.3 -> 20 Elementor Update (Elementor and Elementor Pro) but is stills occuring after I downgraded the website to 19.3.

I am not exactly an expert on JS , but with my very little knowledge about it , I think it’s due to the way how it gets minified as remove whitespace and line-break , in some cases, it just breaks the code when whitespace and line-break are removed

Aha, thank you to be honest.

By the way I will ask my question in another way :

Does your team (the Litespeed Cache plugin team) plan to do something to solve this JS Minifying issue ?

This feature is offered by the plugin so i’m assuming you are working on it (you or some of your coworker) to improve it, update it and handle this particular issues.

Can I (and my coworkers) wait for an update which will fix this JS Minify impossibility ? Or the only solution is to exclude the file (and so to lose the minify feature on these specific files) ?

I’m afraid to say , exclude is the only solution ??