Improve errors handling in config resolution about prettier-eslint HOT 3 CLOSED

Ah yes! Happy to accept a pull request to make that better 👍

from prettier-eslint.

I'm dealing this too, makes me wonder if the quick fix is to run eslint first for code quality and let it error out if the config is bad, then run prettier-eslint.

What's the suggested behavior/API for this? It will ignore eslint and go on with prettier by itself UNLESS there is an explicit config setting? If there is an eslint config settings file and it's invalid then error out?

Just adding some details/questions.

Current lint scripts:

"lint:docs": "./node_modules/.bin/prettylint \"*.md\"",
"lint:fix": "./node_modules/.bin/prettier-eslint --write \"**/*.{js,jsx}\" && ./node_modules/.bin/prettylint \"*.json\" --fix",
"lint:quality": "./node_modules/.bin/eslint \"**/*.{js,jsx,json}\" --max-warnings=0",
"lint:style": "./node_modules/.bin/prettier-eslint --list-different \"**/*.{js,jsx}\" && ./node_modules/.bin/prettylint \"*.json\"",

from prettier-eslint.

Stale issue

from prettier-eslint.