It wasn't ever necessary. Still allow configuring this path in the GUI in case of different paths to static files for scratch-blocks.

Otherwise the VM can't JSON.load it.

If the app is loading with an initial project id, don't try to load the default project. Previously, this data would load on top of the project being loaded.

Does not fix the issue of blocks not loading in the blocks pane, which appears to be separate.

With jscodeshift thank God

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

Move layout styles from component stylesheets to the GUI, or the component that is placing the component.

Add a new `Box` component to control layouts, basically giving a convenient way to lay out with flexbox.

Use `Box` as the output component for any component that may need to be passed layout options. The props passing convention allows giving layout props to the final `Box` component, making wrapping with another `Box` unnecessary in some cases.

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

Move behavior-related components to "containers", leave presentation components in "components".

While doing so:
- Use ProjectLoader for loading projects
- Stop using loadEmptyProject and supply empty project data
- Move project loading to App, GUI now receives data (as a string - the vm should receive an object eventually)
- Add logging

This way we can have a consistent style for Node and web code.

Thanks to babel-loader and babel-eslint, we can use the same linting everywhere.  This makes our imports easier since we don't need to think about the extension.

Also export things more succinctly in src/index.js