```evaluateJSXFile``` is intended to be a public method -- people who write plugins are definitely going to need to be able to execute JSX in the short term, and having a semi-convenient way to do it with files is nice. (The private method is ```_executeJSXFile```, which behaves a little differently with respect to return values so that it can be used for things that yield more than just a JavaScript result.)

However, there's a separate issue. Since the layerSVG.jsx is in core, we should probably expose its functionality through a specific API call (that's what we do for everything else). In general, ```evaluateJSXFile``` should NOT be used by a plugin to execute a JSX file that is in core. It should only be used by a plugin to execute IT'S OWN JSX files.

So, I think the right thing to do here is add an API to core that is something like ```_generator.saveLayerSVGToFile```. I'll make this change.