These aren't necessary to update in realtime, so throttle them to once every 30ms

https://greenkeeper.io/

https://greenkeeper.io/

https://greenkeeper.io/

* Remove unnecessary dev dependencies

* Use large range on true "dev" dependencies

The exact versions of these dependencies are not important for building, so give them large ranges in order to quiet down greenkeeper.

I did not split them between dependencies and devDependencies because a package's dependencies are installed whenever the package is installed as a dependency. Installing all of these would be obnoxious and unnecessary.

https://greenkeeper.io/

https://greenkeeper.io/

Using postcss-modules-values with imported values failed on our current basic usage; it is apparently not mature enough to be used yet.

The syntax used by postcss-simple-vars is already familiar to most people familiar with modern CSS build systems.

https://greenkeeper.io/

Closes #99

https://greenkeeper.io/

Closes #112

https://greenkeeper.io/

Closes #82

https://greenkeeper.io/

https://greenkeeper.io/

https://greenkeeper.io/

Closes #95

https://greenkeeper.io/

https://greenkeeper.io/

* Covers parts of these issues: GUI layout panes (#69), sprite libraries (#12), import buttons (#64), menu bar (#67), and sprite info area (#53)

~ Refactored layout pane structure by removing `display: flex` from `.box`, by default. Declaring flex instead only where specifically needed. This helped fix layout quirks, and should help us avoid hard to find issues related to nested flex boxes

~ Added descriptive classnames to boxes/containers/wrappers. Moved more padding, margins + layout into these wrappers to help with component reusability.

~ Set up a spacer unit variable inside `gui.css`, to start keeping consistent padding, margins and rounded corners between panes. Used [CSS/PostCSS Modules](https://github.com/css-modules/postcss-modules-values) to avoid SCSS dependency.

~ Refactored inline styles from JSX, into CSS files. 2 reasons: a) prepping for reuse of CSS Module variables. b) Feels easier to debug complex flex layouts when all the styles are in one place vs JS/HTML/CSS syntax mixed together

~ Added menu bar into layout via new component, and sprite info header in sprite selector pane, with stubs for the labels + forms. Sprite items are correctly scrolling, while leaving the header fixed, in Chrome. Mostly working in FFx. Not working in Safari, IE yet.

~ Style pass on library modal

~ Experimenting with a few different transition styles: Logo in menu bar, sprite library items, Add buttons.

https://greenkeeper.io/

Closes #92

https://greenkeeper.io/

Improves performance by comparing sprite info values (rather than object identities), and by excluding irrelevant data from this comparison.

https://greenkeeper.io/

https://greenkeeper.io/

https://greenkeeper.io/

The previous method of configuring the port number was not cross-platform.  Resolves #20

The inline css method gives us nothing that CSS modules can't give us. This puts the project more in line with the way www works, and makes CSS actually readable.

Using class names gives us full control of the modal styles.

In preparation to split the sprites from the stage, start managing the target list state in a single place.

This removed our vendor files before. Prevent anything else from happening in the future

After doing this, new rules began applying for some reason:

`eol-last` only began taking the 'always' parameter as of 3.6.0, so I needed to update eslint.
`no-unused-var` started warning about process.env after updating the config structure
`comma-dangle` decided to start working, maybe because of the upgrade to eslint?  Autofixed with --fix

Includes rules missed in the first pass of eslint rules

Previously eslint ignored .jsx files :|

When the package is installed as a dependency, it should warn the installer that React is a peerDependency.  When installed this way, the devDependencies won't be installed, so only one version of React will be present. However when it's installed as a standalone project, React should be installed automatically as a devDependency.

I think this gives us the best of both worlds — simple development setup as well as supporting usage as an installed package.