Uncaught SyntaxError: unexpected token: keyword 'const' when minifying javascript files with constants and backticks `

[ioweb-gr]

Preconditions (*)

Please check this line of code for example

magento2/lib/web/jquery/bootstrap/collapse.js

Line 35 in 7e794ce

const EVENT_KEY = `.${DATA_KEY}`

1. Magento 2.4.4

Steps to reproduce (*)

1. Set the following config options

dev/js/merge_files - 1
dev/js/enable_js_bundling - 1
dev/js/minify_files - 1

2. Create a few orders
3. Deploy static files and visit the orders grid
4. Watch the javascript errors

Expected result (*)

1. No javascript errors

Actual result (*)

Uncaught SyntaxError: unexpected token: keyword 'const'[collapse.min.js:4:30](https://dev.safeblock.gr/static/version1652532411/adminhtml/Magento/backend/en_US/jquery/bootstrap/collapse.min.js)

Uncaught SyntaxError: unexpected token: keyword 'const'

The minified javascript files become broken like this because there are no delimiters for each new line when backticks are used.

define(["jquery","./util/index","./dom/data","./dom/event-handler","./dom/manipulator","./dom/selector-engine"],function($,Util,Data,EventHandler,Manipulator,SelectorEngine){'use strict';const defineJQueryPlugin=Util.defineJQueryPlugin;const executeAfterTransition=Util.executeAfterTransition;const getElement=Util.getElement;const getSelectorFromElement=Util.getSelectorFromElement;const getElementFromSelector=Util.getElementFromSelector;const reflow=Util.reflow;const typeCheckConfig=Util.typeCheckConfig;const VERSION='5.1.3'
const NAME='collapse'
const DATA_KEY='bs.collapse'
const EVENT_KEY=`.${DATA_KEY}`const DATA_API_KEY='.data-api'
const Default={toggle:true,parent:null}

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ioweb-gr. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hi @ioweb-gr ,
Thank you for reporting and collaboration. However this issue is a duplicate of #35325. We are closing this issue. Please move on to this ticket for latest updates/solutions.
Thank you.

[ssx]

Patch: https://gist.github.com/ssx/275bc6c9674277ed8d26592235f1cc6b