On other projects, I've used the Prettier code formatter via the official Atom package. It saves a lot of time hassling with code formatting, and not having it enabled for Atom is causing me to waste a lot of time fixing linting errors.

On Atom, we're using JS Standard Style, which conflicts with the Prettier's default formatting. This is okay, because the Prettier package can run eslint --fix automatically after performing its own formatting, but it requires a bit of configuration. To support it, I've added an .eslintrc.json file to the root of the module. This needs to pull in the shared ES Lint configurations associated with Standard Style, but since we avoid installing dev dependencies in our root package.json, I've added those linting configurations to script/package.json and am including them with an explicit path.

With this change, you can now get nice auto-formatting when you install Prettier Atom and enable ES Lint support in the package settings.

We have a lot of files that aren't formatted with prettier, so this might generate a bit of churn initially, but I think the productivity savings will be worth it in the long run.

One particular issue is that Atom's source files don't have a consistent style with respect to spaces inside of curly brackets. Prettier defaults to having spaces ({ foo: "bar" }, but standard doesn't seem to care, and we have examples of both styles in this repo. It's possible to override the default and remove spaces, but it's more typical style to include these spaces, so I'm going to leave the current default in place.

cc @atom/maintainers