Nicky McCurdy

It should pick up `package.json` now, maybe Prettier is out of date?

> The only one I have reservations about is the automatic formatting. Out of curiosity, what don't you like about it? How would you feel about adding it with a...

Seems related to #25

What error are you getting?

I think we should be fine with just a README.md and CONTRIBUTING.md (eventally), unless you have suggestions for other wiki pages.

I'm going to see if I can swap in `sinon-chrome` similarly to #87 before I merge this. Maintaining mocks manually is a lot of churn.

I've fixed merge conflicts and several configuration issues. Now that we're using `sinon-chrome` we no longer need to develop complex mocks and can just focus on implementing the options tests...

Good question, maybe we could use a language detection library and fall back to Markdown when it's unknown or looks like snippets from multiple languages.

Some resources for language detection: - https://prettier.io/docs/en/api.html#prettiergetsupportinfo-version - https://highlightjs.readthedocs.io/en/latest/api.html#highlightauto-value-languagesubset - https://www.npmjs.com/package/language-map - https://www.npmjs.com/package/language-detect

As a temporary workaround, I uninstalled Prettier globally (`npm r -g prettier`) after setting up `add-node-modules-path`. Now `prettier-emacs-mode` will only format buffers if it's in a project with `prettier` installed...