Install eslint in frontend, backend & deploy folders separately, or once in root?

Question

I'm working on a tutorial project that has backend, frontend and deploy folders in the project root. Each of them has a package.json and thus a node_modules folder. The frontend is a create-react-app and I just spent a half hour dialing in the eslint config. Then I realized there is no eslint installed in the backend or deploy folders.

Should I install eslint separately in each of those then copy my .eslintrc file over, or nuke it from the front end and install it once in the root (one lint to rule them all)?

My fear with the latter is that there will be lingering eslint settings in my [un-ejected] create-react-app that will fight with any installation in the parent (root) folder.

Answer 1

If you develop a back-end under NodeJS runtime, you could use ESlint, and preferably use a separate ESlint config files, thus you could define your rules as you want, may you will use an Airbnb javascript style guide on your frontend, so you will be comfortable later.