Please check if the bug still exists when using js2-jsx-mode (if applicable). If so, it is most likely an upstream bug and should be reported there.