No Code Attached Yet
avatar dgrammatiko
dgrammatiko
6 May 2022

Screenshot 2022-05-06 at 14 23 21

Problem identified

Joomla 4 emits/creates ES5 javascript next to the current ES2018 ones. That was done because Internet Explorer was still alive but in few weeks it will be officially dead. Most of the tools also will adjust to this change, specifically autoprefixer and preset-env will move that browser to the dead ones. Thus the project has 2 options:

  • adjust the scripts to keep creating the ES5 files (which are already broken, missing essential polyfills, etc, basically they are useless)
  • or adjust the build tools to stop creating the ES5 files

Proposed solution

The proposal is to (obviously) drop the dead, unusable, ES5 files. The process needs some adjustments for the build tools and also adjusting the joomla.assets.json files.

Open questions

PS: If there's a decision to drop them I'll put the work to make it happen but time is critical here and this should be in the 4.2 early enough to have as much testing as possible

Context:

avatar dgrammatiko dgrammatiko - open - 6 May 2022
avatar joomla-cms-bot joomla-cms-bot - change - 6 May 2022
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 6 May 2022
avatar dgrammatiko dgrammatiko - change - 6 May 2022
The description was changed
avatar dgrammatiko dgrammatiko - edited - 6 May 2022
avatar dgrammatiko dgrammatiko - change - 7 May 2022
Status New Closed
Closed_Date 0000-00-00 00:00:00 2022-05-07 07:35:50
Closed_By dgrammatiko
avatar dgrammatiko dgrammatiko - close - 7 May 2022
avatar pl71
pl71 - comment - 23 Oct 2022

and... es5 files are still here.

<script src="/media/com_finder/js/finder-es5.min.js
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37755.

Add a Comment

Login with GitHub to post a comment