Getting errors with JSMin "JSMin had a possible error minifying:"

Created on 3 June 2021, over 3 years ago
Updated 20 November 2023, 12 months ago

Problem/Motivation

I implemented the JSMin library - and my log file produces 4 warnings/errors about minifying.
If I use another compressor (I tried both Jsqueeze and jsmin+) , clear cache, clear report, then I get no errors. I'm unclear how to debug this reason. as JSMin has been sedentary for 3+ years, I doubt it's jsmin :)

Steps to reproduce

Enable JSMin as compressor in Advagg.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Active

Version

4.0

Component

Compression/Minification

Created by

🇺🇸United States jshimota01 Portland, OR

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇸United States froboy Chicago, IL

    Same issue here. Saw similar errors and the admin menu was broken on some Webform Results Download pages. Switching to Jsqueeze resolved the issue.

  • 🇮🇷Iran tsotoodeh

    Same issue here. Saw similar errors and the admin menu was broken on some Webform Results Download pages. Switching to Jsqueeze resolved the issue.

    Digging on an old issue! Make sure your hosting provider enabled the extensions, otherwise it is better to submit a complete issue with required steps to reproduce the issue.

  • I'am having the same issue.
    Just installed the jsmin for homebrew to test localhost.
    Some files are not minified due to an error.
    Has it something todo with PHP 8.0? I don't know.

  • 🇸🇰Slovakia coaston

    I do have the same issue on D10 and PhP 8.1 ,any update ?

  • 🇬🇧United Kingdom tce

    I get the error:

    Message = JSMinPlus had a possible error minifying: themes/contrib/seven/js/nav-tabs.js. Using uncompressed version. Error: Parse error: Unexpected token; token : expected in file '[inline]' on line 39

    Any solutions for this?

Production build 0.71.5 2024