Hello,
I wrote an extension with arrow function and class fields. Everything is working in Firefox but I can’t submit my addon as the validator does not support this syntax.
It’s very annoying as the code works, extension is already published on chrome store…
When will the validator be upgraded?
Is there a way to bypass it in this case?
Thanks for your help!
Arrow functions aren’t the issue, but class fields are. There are multiple issues filed on it, like https://github.com/mozilla/addons-linter/issues/2758
Sadly issues with the syntax support of the validator come up again and again 
I think it’s the issue, I have some classes with only arrow function and the validator fails on them too
Why mozilla stays in this situation? This is very bad 
No wonder google chrome goes up…
If you use an arrow function to define a class method, unless you define it in the constructor (which is by the way a mighty fine way to do it for now, if you don’t like babel), will require the usage of a class field. As such, not the arrow function is the issue, but the class field syntax. If you were to define the same arrow function as a class member but in the constructor, the validator would be just fine with it.