Since ESLint doesn't let us disable auto-fix for individual rules, and the capitalized-comments rule, while useful, can be annoying in editors when "auto-fix on save" is enabled.

SamVerschueren/vscode-linter-xo#78 (comment)

It's not recommended to use document.cookie directly as it's easy to get the string wrong. See sindresorhus/eslint-plugin-unicorn#299 and https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie Instead, the user should use a cookie library.

I guess we should only prevent setting document.cookie? There might be valid reasons to read it?

The @typescript-eslint/eslint-plugin provides a recommended config which turn off some Eslint rules that conflicts or doesn't work well with TypeScript.

For example in a types.d.ts file with the following code:

type MyType = {};

export {MyType};

t

Using the following config but xo doesn't play nicely with react closing syntax:
I'm guessing I don't require an .eslint config to make this work:

{
  "name": "react-starter",
  "version": "1.0.0",
  "description": "Highly opinionated starter web application for react client side projects",
  "main": "index.js",
  "scripts": {
    "start": "parcel index.html -p 4444",
    "build": 

Problem

If the package.json contains some syntax errors atom-lint task never ends and after a while it makes atom unresponsive.
The only solution to allow the task to complete a