api.md

API

reactToWebComponent(ReactComponent, React, ReactDOM, options) takes the following:

• ReactComponent - A React component that you want to convert to a Web Component.

• options - An set of parameters.

  • options.shadow - ("open", "closed", or undefined) Use the specified shadow DOM mode rather than light DOM.

  • options.events - Array of camelCasedProps to dispatch as custom events or a Record of event names to their associated Event constructor options.

    • When dispatching events from named properties, "on" is stripped from the beginning of the property name if present, and the result is lowercased: the property onMyCustomEvent dispatches as "mycustomevent".

  • options.props - Array of camelCasedProps to watch as String values or { [camelCasedProps]: "string" | "number" | "boolean" | "function" | "json" }

    • When specifying Array or Object as the type, the string passed into the attribute must pass JSON.parse() requirements.
    • When specifying Boolean as the type, "true", "1", "yes", "TRUE", and "t" are mapped to true. All strings NOT begining with t, T, 1, y, or Y will be false.
    • When specifying Function as the type, the string passed into the attribute must be the name of a function on window (or global). The this context of the function will be the instance of the WebComponent / HTMLElement when called.
    • If PropTypes are defined on the React component, the options.props will be ignored and the PropTypes will be used instead. However, we strongly recommend using options.props instead of PropTypes as it is usually not a good idea to use PropTypes in production.
    • If options.props is an array of string (prop names), the type of those props will be String.

  A new class inheriting from HTMLElement is returned. This class is of type CustomElementConstructor can be directly passed to customElements.define as follows:

customElements.define("web-greeting", reactToWebComponent(Greeting))

Or the class can be defined and used later:

const WebGreeting = reactToWebComponent(Greeting)

customElements.define("web-greeting", WebGreeting)

var myGreeting = new WebGreeting()
document.body.appendChild(myGreeting)

Or the class can be extended:

class WebGreeting extends reactToWebComponent(Greeting) {
  disconnectedCallback() {
    super.disconnectedCallback()
    // special stuff
  }
}
customElements.define("web-greeting", WebGreeting)

Components can also be implemented using shadow DOM with either open or closed mode.

const WebGreeting = reactToWebComponent(Greeting, {
  shadow: "open",
})

customElements.define("web-greeting", WebGreeting)

var myGreeting = new WebGreeting()
document.body.appendChild(myGreeting)

var shadowContent = myGreeting.shadowRoot.children[0]

If propTypes are defined on the underlying React component, dashed-attributes on the webcomponent are converted into the corresponding camelCase React props and the string attribute value is passed in.

function Greeting({ camelCaseName }) {
  return <h1>Hello, {camelCaseName}</h1>
}
Greeting.propTypes = {
  camelCaseName: PropTypes.string.isRequired,
}

customElements.define(
  "my-dashed-style-greeting",
  reactToWebComponent(Greeting, {}),
)

document.body.innerHTML =
  '<my-dashed-style-greeting camel-case-name="Christopher"></my-dashed-style-greeting>'

console.log(document.body.firstElementChild.innerHTML) // "<h1>Hello, Christopher</h1>"

If options.props is specified, R2WC will use those props instead of the keys from propTypes. If it's an array, all corresponding kebob-cased attr values will be passed as strings to the underlying React component.

function Greeting({ camelCaseName }) {
  return <h1>Hello, {camelCaseName}</h1>
}

customElements.define(
  "my-dashed-style-greeting",
  reactToWebComponent(Greeting, {
    props: { camelCaseName: "string" },
  }),
)

document.body.innerHTML =
  '<my-dashed-style-greeting camel-case-name="Jane"></my-dashed-style-greeting>'

console.log(document.body.firstElementChild.innerHTML) // "<h1>Hello, Jane</h1>"

Typed Props

If options.props is an object, the keys are the camelCased React props and the values are any one of the following built in javascript types. This is the recommended way of passing props to r2wc.

"string" | "number" | "boolean" | "function" | "json"

"json" can be an array or object. The string passed into the attribute must pass JSON.parse() requirements.

"string" | "number" | "boolean" | "function" | "json" props

function AttrPropTypeCasting(props) {
  console.log(props) // Note
  return <h1>Hello, {props.stringProp}</h1>
}

customElements.define(
  "attr-prop-type-casting",
  reactToWebComponent(AttrPropTypeCasting, {
    props: {
      stringProp: "string",
      numProp: "number",
      floatProp: "number",
      trueProp: "boolean",
      falseProp: "boolean",
      arrayProp: "json",
      objProp: "json",
    },
  }),
)

document.body.innerHTML = `
  <attr-prop-type-casting
    string-prop="iloveyou"
    num-prop="360"
    float-prop="0.5"
    true-prop="true"
    false-prop="false"
    array-prop='[true, 100.25, "👽", { "aliens": "welcome" }]'
    obj-prop='{ "very": "object", "such": "wow!" }'
  ></attr-prop-type-casting>
`

/*
  console.log(props) in the functions produces this:
  {
    stringProp: "iloveyou",
    numProp: 360,
    floatProp: 0.5,
    trueProp: true,
    falseProp: false,
    arrayProp: [true, 100.25, "👽", { aliens: "welcome" }],
    objProp: { very: "object", such: "wow!" },
  }
*/

Function props

When Function is specified as the type, attribute values on the web component will be converted into function references when passed into the underlying React component. The string value of the attribute must be a valid reference to a function on window (or on global).

Note: If you want to avoid global functions, instead of passing an attribute you can pass an events object in options, and listen on events using addEventListener on the custom element. See below.

function ThemeSelect({ handleClick }) {
  return (
    <div>
      <button onClick={() => handleClick("V")}>V</button>
      <button onClick={() => handleClick("Johnny")}>Johnny</button>
      <button onClick={() => handleClick("Jane")}>Jane</button>
    </div>
  )
}

const WebThemeSelect = reactToWebComponent(ThemeSelect, {
  props: {
    handleClick: "function",
  },
})

customElements.define("theme-select", WebThemeSelect)

window.globalFn = function (selected) {
  // "this" is the instance of the WebComponent / HTMLElement
  const thisIsEl = this === document.querySelector("theme-select")
  console.log(thisIsEl, selected)
}

document.body.innerHTML =
  "<theme-select handle-click='globalFn'></theme-select>"

setTimeout(
  () => document.querySelector("theme-select button:last-child").click(),
  0,
)
// ^ calls globalFn, logs: true, "Jane"

Event dispatching

As an alternative to using function props, the events object insructs r2wc to dispatch a corresponding DOM event that can be listened to on the custom element itself, on ancestor elements using bubbles, and outside of any containing shadow DOM using composed.

function ThemeSelect({ onSelect }) {
  return (
    <div>
      <button onClick={() => onSelect("V")}>V</button>
      <button onClick={() => onSelect("Johnny")}>Johnny</button>
      <button onClick={() => onSelect("Jane")}>Jane</button>
    </div>
  )
}

const WebThemeSelect = reactToWebComponent(ThemeSelect, {
  events: { onSelect: { bubbles: true } } // dispatches as "select", will bubble to ancestor elements but not escape a shadow DOM
})

customElements.define("theme-select", WebThemeSelect)

document.body.innerHTML = "<theme-select></theme-select>"

setTimeout(() => {
  const element = document.querySelector("theme-select")
  element.addEventListener("select", (event) => {
    // "event.target" is the instance of the WebComponent / HTMLElement
    const thisIsEl = event.target === element
    console.log(thisIsEl, event.detail)
  })
  document.querySelector("theme-select button:last-child").click()
}, 0)
// ^ calls event listener, logs: true, "Jane"

Note: events and props entries should not be used for the same named property. During initial setup, the event handler will overwrite the function property handler, and if the attribute changes after construction, the new function property handler will overwrite the event handler.