A React component that helps you to mount your WebComponents.
- You have the CustomElement script available under a known URL.
There are two ways to use CustomElementReactMount
:
- Set up scripts on bootstrap
You can conveniently configure all elements that you might use in your application at any time prior to the use of the actual elements. The scripts will load on the first use of each element.
import CustomElementReactMount from 'custom-element-react-mount'
const App = () => {
CustomElementReactMount.addComponentURLMapping({
'my-custom-element': 'path-to/my-custom-element.js',
'foo-element': 'https://example.com/foo-element.js',
});
return (
<div>
<MyActualApp /> // somewhere here you can mount your custom-elements
</div>
)
}
// for example:
const MyActualApp = () => (<div>
<header><MyHeader /></header>
<section>
<CustomElementReactMount>
<my-custom-element></my-custom-element> // no need to pass src as
// it's already configured above
</CustomElementReactMount>
</section>
</div>)
- Pass down the URL as a prop
If you don't have a bootstrap step, or for some reason wish to specify the script directly with the element itself, you can pass the src directly as a prop. This will override the above configuration if exists:
import CustomElementReactMount from 'custom-element-react-mount'
const myComponent = () => {
return <CustomElementReactMount src="path-to/my-custom-element.js">
<my-custom-element/>
</CustomElementReactMount>
}
If you are using babel to transpile your custom element classes, the browser might fail with the following error:
Uncaught TypeError: Failed to construct 'HTMLElement': Please use the 'new' operator, this DOM object constructor cannot be called as a function.
The reason lies in the way babel tanspiles the code. this can be fixed by adding the following plugin babel to your setup: