Adds pre-commit hooks

[johnatawnclementawn]

No description provided.

[johnatawnclementawn]

Hey @chrabyrd - @jacobtylerwalls and I were stubbing our toes on failing tests. It looks like CI is caching the dev dependencies which were being changed here (not picking up the addition of the helper that allows prettier and eslint to play nicely).
It seems like there are a handful of options - one is to point to a specific commit hash on the dev-dependencies branch (as I've done here). The other could be to add an npm cache clean to the GH action, but we tested that locally and it didn't seem to help.

[chrabyrd]

Hey @chrabyrd - @jacobtylerwalls and I were stubbing our toes on failing tests. It looks like CI is caching the dev dependencies which were being changed here (not picking up the addition of the helper that allows prettier and eslint to play nicely). It seems like there are a handful of options - one is to point to a specific commit hash on the dev-dependencies branch (as I've done here). The other could be to add an npm cache clean to the GH action, but we tested that locally and it didn't seem to help.

@johnatawnclementawn could this be a package-lock.json issue? I don't love the idea of de-standardizing package.json just to make a test runner pass. I'd rather find a solution instead of a workaround, that way if this happens with developers out in the wild we have an answer for them.

[chrabyrd]

lgtm!