Separate into Opal bootstrap and loader

[wied03]

I've been wondering if this loader is really doing 2 things: presenting a "bootstrapped" version of Opal in Node and serving as webpack loader. What if this was split into 2 packages

1. Opal NPM - could also be called Opal bootstrap. This would include the compiler.rb patches, bundlerCheck/Execute, getRubyMetadata, and the getOpal*Filename.js files

2. Webpack loader - everything else

This would make it easier to implement #7 because a separate plugin could be developed that could modify webpack's "load path" but take advantage of the Opal NPM code above just like the loader does. No urgency here, but any thoughts @cj ?

[wied03]

@cj - any opinion on who "owns" the new project (github and NPM) ?

[wied03]

Also, looks like https://github.com/anthonny/opal-npm-wrapper is out there, although there are some things that would need tweaking with that.

[wied03]

I might raise an issue and ask how willing they would be to cover the cases the code in the repo does.

[cj]

any opinion on who "owns" the new project (github and NPM) ?

I don't mind :)

Interesting. Let me know if you get a hold of him. Should we just fork it for now?

[wied03]

No urgent need for me to do anything, I'm content to wait and see how it plays out personally.