With this, we can use prettier in pre-commit without getting errors stemming from the formatting changes. Previously we did because the eslint's .js parser was not modern enough to support the formatting changes.
By switching to use the @babel/eslint-parser we are fine for now at least, and I think in the future as well, because we end up using a parser that is provided by babel, which is also what we use to transform the .js into something else.
With this, we can use prettier in pre-commit without getting errors stemming from the formatting changes. Previously we did because the eslint's .js parser was not modern enough to support the formatting changes.
By switching to use the
@babel/eslint-parser
we are fine for now at least, and I think in the future as well, because we end up using a parser that is provided by babel, which is also what we use to transform the .js into something else.