Deprecate renderInstance

[FlorianRappl]

New Feature Proposal

For more information, see the CONTRIBUTING guide.

Description

Right now piral-core uses the more explicit createInstance while piral introduces renderInstance. The latter should be deprecated and only one way should be used.

In 1.0 renderInstance would then be removed.

Background

Having "two ways" (or to be more precise: one convenience way on top of another way) is not good for documentation and transparency. With the more explicit createInstance the render call of react-dom would need to be called explicitly, which opens the door to more optimizations and customizations for the end-user.

Discussion

In general piral should only provide

• resolution of peer dependencies (i.e., selection of dependency versions)
• inclusion of some "standard" plugins via piral-ext

but nothing more. Consequently, the standard template(s) could be improved, too - if they work for piral-core they'd work for piral, too (only by exchanging the package name).