Add option to set current React instance.

[rmorshea]

This line makes it hard to work with IDOM client-side because it's bound to the React instance that was built into the client. However we could work around that by doing the following instead I think:

let currentCreateElement = react.createElement;
let html = htm.bind(currentCreateElement);

function bindElementConstructor(createElement) {
  if (createElement !== currentCreateElement) {
    html = htm.bind(createElement)
  }
}

This way downstream clients can set what React instance is being used

[rmorshea]

See here as well: developit/htm#203

[rmorshea]

Doing this would break the component cookiecutter, but I had been thinking that we should make the components completely independent. Instead of just doing:

React.createComponent(userModule.userComponent)

The userModule would have a mount function that accepted the element in the DOM they should attach to. From there it'd be entirely up to the component on what it wants to do. The component could be React or it could even be Vue. The point is that it'd be completely separate and thus simpler to deal with.

This does make the idea of just people able to idom.install react components a bit awkward though since they won't know to abide by the same rules. There's probably a way to work around that though.

I think the fact that I need this rollup plugin to mangle the imports into the right thing tells me I'm trying to do something that I shouldn't be doing.

[rmorshea]

Maybe the interface is userModule.mount(component, element) which would mean that you could just make userModule.mount = React.render as well as give yourself the flexibility to work with another (or even no) framework.

[rmorshea]

This change should be made before updating idom-jupyter, and friends.

[rmorshea]

Actually these are really two separate issues. The latter is easier to solve and can be done independently. See: #4

[rmorshea]

This needs some more thought