install-peerdeps | line interface to install an NPM package | Command Line Interface library

See the docs: https://prettier.io/docs/en/options.html#quotes

It specifically states "JSX quotes ignore this option – see jsx-single-quote."

Set jsxSingleQuote to true

Run npm install --legacy-peer-deps and they will install successfully.

Looking at your package.json and comparing it to the peer dependencies listed for eslint-config-airbnb, you already have all the peer dependencies in your package.json as dev dependencies. (They were probably added there when you ran the npx install-peerdeps command but then that command tried to run npm install and failed.)

Optional catch binding was introduced in ES2019.

The specified ESLint version should be used with Node version that supports it (10 or later).

You'll have to use npm audit and actually read the audit log. In there will be advice on which versions can be installed to fix vulnerabilities.See https://docs.npmjs.com/cli/audit for more information on npm audit.

You can get a report of all vulnerabilities using npm audit. In that report for each vulnerability you will also see a way to fix it. When you use npm audit fix you are telling npm to execute those fixes. Npm however will not automatically install fixes that might break your project, such as major versions changes. You'll have to manually execute the npm install commands for those if you decide the vulnerability is more important than having to deal with the possible breaking change.

Another common warning are peer dependency warnings. Peer dependencies specify not dependency, but compatibility. Check out this post for a way better explanation on peer dependencies: https://stackoverflow.com/a/34645112/1016004

You can see a peer dependency warning for 2 reasons: the specified peer dependency is missing, or the peer dependency is of the wrong version. In both cases you will have to figure out the correct response yourself. The core question to answer is whether you can install the dependency in your project:

• Do you use any deprecated features that will be removed in an update, do any breaking changes apply to your code, ...?
• Do you have to revert to a version with a known vulnerability that you use in such a way that it might endanger user data, ... ?

The simple solution, not recommended for production, is to just manually try to run npm install for both the vulnerabilities and peer dependencies with the proposed versions. Be sure to have version control or backups so that you can revert if you end up with more errors than you started with.

If the simple solution doesn't cut it you'll have to look for other versions of packages that are part of the unsolvable constraints. Maybe previous versions of any of those packages can work together?

Without digging into the issue and finding specific point of failure I decided on a fresh start.

• Delete global node modules.
• Delete all NON core Atom plugins AND themes.
• uninstall Atom.
• reinstall Atom.
• install ESLint and supporting dependencies only.

Doing that I was able to run ESLint with no issues. My assumption in all of this is there was a conflict in a plugin or theme. From there installing my core tool plugins was successful.