Responding to my own question, it was the SEO engi...
# suitecommercem
Matias Bonifacino
09/24/2020, 5:11 PMResponding to my own question, it was the SEO engine that was broken. Weird thing is a buddy of mine is on 2019.2.4 and he had an error on the SEO engine but was not getting the flickering.
s
Steve Goldberg
09/24/2020, 5:19 PMBroken how? (And did you fix it?)
m
Matias Bonifacino
09/25/2020, 3:45 PMWe used let and const for some of our javascript files because we realized it was working, but turns out it was actually breaking the SEO engine, after fixing it we didn’t get a flash anymore.
Matias Bonifacino
09/25/2020, 3:49 PMAlso, we saw things like () => to name functions that would break it, or adding a comma on the last dependency of the function() when defining a module would also break it
Matias Bonifacino
09/25/2020, 3:49 PMIt was an interesting experience to fix given we have more than 50 extensions and had to redeploy like 30 of them
s
Steve Goldberg
09/25/2020, 4:02 PMYes, we only support ES5
m
Matias Bonifacino
09/25/2020, 6:02 PMdo you have an idea on how long it’s going to be until you support newer versions?
s
Steve Goldberg
09/28/2020, 9:58 AMNo. Keep in mind that we still have to support IE11 and so we likely won't support newer versions of ECMAScript until we no longer have to support IE
m
Mark
09/28/2020, 3:10 PMWould there be any issues with transpiling ES6 to ES5 via a gulp task when deploying extensions?
s
Steve Goldberg
09/28/2020, 3:29 PMc'est possible
Steve Goldberg
09/28/2020, 3:30 PMWe have a transpilation process for TypeScript
Steve Goldberg
09/28/2020, 3:31 PMBut AFAIK we have no plans to introduce one
m
Mark
09/28/2020, 4:22 PMNice! I will have to look into getting that configured.
7 Views