NPM Resource Changed ? Pending

User tests: Successful: Unsuccessful:

avatar dgrammatiko
dgrammatiko
10 Apr 2021

Pull Request for Issue #25639 .

Summary of Changes

When I refactored the build tools I left the ES5 babel config basically unconfigured. The reason was I was expecting that we could come up with an action plan (eg a broader talk about polyfills, #32315 (comment)). This obviously didn't happen and so here's the missing configuration.

Testing Instructions

Apply the branch
Run npm i
CHECK WITH IE and report any console errors.

Attention there are known missing polyfills that this PR IS NOT addressing. This PR just ensures modern code is transpilled so IE can run it (this includes also a gazillion of polyfills but there are many DOM related parts that are not polyfillable from babel)

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

Documentation Changes Required

avatar dgrammatiko dgrammatiko - open - 10 Apr 2021
avatar dgrammatiko dgrammatiko - change - 10 Apr 2021
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 10 Apr 2021
Category JavaScript Repository NPM Change
avatar dgrammatiko
dgrammatiko - comment - 17 Apr 2021

@Fedik can you test this one with IE11 and report back the errors logged?

avatar Fedik
Fedik - comment - 17 Apr 2021

well, let's forget about IE 11 ?
I tested, but there bunch of syntax error, because arrow function and stuff, because of es6

I not sure it worth the time that much

avatar dgrammatiko
dgrammatiko - comment - 17 Apr 2021

well, let's forget about IE 11

Actually, you're right, IE will be dead in 4 months so there's not point https://death-to-ie11.com

avatar dgrammatiko dgrammatiko - close - 17 Apr 2021
avatar dgrammatiko dgrammatiko - change - 17 Apr 2021
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2021-04-17 22:17:23
Closed_By dgrammatiko
Labels Added: NPM Resource Changed ?

Add a Comment

Login with GitHub to post a comment