Skip to content

chore: don't run ESLint on save

Pajamas' Nuxt app is currently setup to run ESLint on save in development mode. While it does make it hard to miss ESLint errors, it can be extremely annoying during development as you might want to write dirty code early on and clean it up once it's ready to be pushed.

Screen_Shot_2021-04-07_at_4.50.56_PM

This removes eslint-loader from Nuxt's config so that we can shamelessly write bad code locally.

We still have the option to run yarn eslint to find catch errors before pushing. Once pushed, the code will be checked in CI anyways.

A follow-up and potentially better option would be to setup husky to setup git hooks and lint on commit or push.

Merge request reports