How to deal with eslint errors in generated .bs.js files?

The generated .bs.js has tons of eslint errors. For example, every switch command generates a “Expected a default case” error. I know ReScript ensures every case is covered but eslint doesn’t know that. Other errors: default-case, no-fallthrough. These are good errors to have in my handwritten code. Should I just turn off eslint for all .bs.js files?

I would just turn of eslint for .bs.js files

3 Likes

Recent nextjs releases provide extra eslint checks, so some people may want to keep those nextjs checks.