feat(runtime): export a render method from the runtime #6245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the current behavior?
It is currently rather difficult to render a Stencil VDOM to a container node. While this is technically not needed by users as you can just use WebAPIs to inject a Stencil element to a page, it helps when integrating Stencil within other environments, e.g. Storybook where you get a VDOM value to render somewhere. Stencil has its own VDOM implementation and we can't just take the one from Preact or other frameworks.
Given that the function is lightweight enough it won't have an impact on the bundle size, as it will be embedded into users bundles.
What is the new behavior?
@stencil/core
now exports arender
method to conveniently render a Stencil VDOM into a DOM node.Documentation
stenciljs/site#1518
Does this introduce a breaking change?
Testing
Added WDIO tests for this.
Other information
I need this for the Storybook integration.