Introduce automated tests, de-lint, and migrate towards best practices

[bugeats]

Hi Nater. I've been using this library for a professional project and it's been very helpful. Thank you for all your hard work.

My project requires conditional formatting, and I'm planning on taking a stab at implementing it. In order to do this, I needed to get some automated tests going.

I was also having trouble with JS bundling, so I de-linted the project and migrated towards some best practices (like lower-case file names).

There's a lot here, but the underlying code should't have changed much.

I added an eslintrc file. Of course, style is often a matter of personal preference, but in this case I strive to model it off the latest JS style guides. If you have an editor that supports eslint, I highly recommend using it.

You can run tests with: npm test. The quicker that tests are completed, the sooner we can be confident about correct implementation of conditional formatting.

Thanks,
-C

[natergj]

Thanks @bugeats
I've been meaning to add testing linting for a while now. This was an extremely useful pull request. It's been published to npmjs.com under version 0.3.0. There are few features I'm hoping to start on after a big application update release at work is complete in a couple weeks. Among them are ability to add comments to a cell, get detailed information about a cell, bulk data population from SQL query and importing a template file. Conditional formatting has been requested a few times, so I'm very glad to hear you're working on that.
Thanks, again!
nater

[bugeats]

Great! I'll be involved for at least as long as it takes for you to pick back up on the project, and I'll let you know how conditional formatting is coming.