npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@shopify/checkout-ui-extensions-react

v0.27.3

Published

React bindings for @shopify/checkout-ui-extensions

Downloads

5,239

Readme

@shopify/checkout-ui-extensions-react

This library provides utilities for writing checkout UI extensions using React.

Installation

$ yarn add @shopify/checkout-ui-extensions-react

Usage

All UI rendering capabilities are built on top of a library called remote-ui. One of the powerful aspects of remote-ui is that it can be the target for JavaScript libraries that support custom (non-DOM) rendering. React is one such library, and remote-ui provides a custom renderer for React that allows you to use all the power of React, while outputting UI mutations that remote-ui can understand.

@shopify/checkout-ui-extensions-react provides a few additional utilities if you are writing a UI extension in React (it also re-exports all the relevant values from @shopify/checkout-ui-extensions). Before you start down this path, though, make sure you are working on an extension that will be complex enough to warrant the additional bundle size of including React. The core API of remote-ui is built to be usable directly, and remote-ui provides other bindings, like this one to htm, that provide some of the ergonomics of React without so much overhead.

To use the React bindings in a UI extension, start by importing React as you normally would. All of the core features of React are available, including hooks, context, and more.

You’ll then import render from @shopify/checkout-ui-extensions-react. This function is a thin wrapper around shopify.extend and @remote-ui/react’s render(). You’ll pass this function the name of an extension that can render UI, and a function that should return the JSX to render when that extension point is run. This function receives the input argument for the extension point.

import {render} from '@shopify/checkout-ui-extensions-react';

// `extensionPoint` is part of the [standard API](../checkout-ui-extensions/src/extension-points/api/standard)
render('Checkout::PostPurchase::Render', ({extensionPoint}) => (
  <Extension extensionPoint={extensionPoint} />
));

interface Props {
  extensionPoint: string;
}

function Extension({extensionPoint}: Props) {
  return <>Extension point: {extensionPoint}</>;
}

If you’ve ever used React on the web, you’re probably used to returning DOM nodes as part of your React components. Because UI extensions execute in a web worker and have no access to the DOM, returning DOM components is an error in UI extensions. Instead, you can return the components you import from @shopify/checkout-ui-extensions-react, which are the equivalent of the DOM in checkout — they are the “leaf” elements, the lowest-level UI primitives that exist.

import {render, Button} from '@shopify/checkout-ui-extensions-react';

render('Checkout::PostPurchase::Render', (props) => <Extension {...props} />);

interface Props {
  extensionPoint: string;
}

function Extension({extensionPoint}: Props) {
  return (
    <Button
      onPress={() => {
        console.log(`Extension point: ${extensionPoint}`);
      }}
    >
      Log extension point to console
    </Button>
  );
}

Other React-specific APIs

useExtensionApi()

useExtensionApi is a custom React hook that gives you access to the full input argument provided to your extension point (this is the value that, if you were registering an extension point directly with shopify.extend, would be passed as the second argument to your callback). This allows you to access and call the main APIs between your extension and Shopify anywhere in your React component.

If you are using TypeScript, you can supply the name of the extension point as a type parameter to this function. Doing so will refine the return type to be exactly the input type for that extension point, so make sure you pass the name of the extension you are actually rendering.

import {
  render,
  useExtensionApi,
  Button,
} from '@shopify/checkout-ui-extensions-react';

render('Checkout::PostPurchase::Render', () => <Extension />);

function Extension() {
  const {extensionPoint} = useExtensionApi<'Checkout::PostPurchase::Render'>();

  return (
    <Button
      onPress={() => {
        console.log(`Extension point: ${extensionPoint}`);
      }}
    >
      Log extension point to console
    </Button>
  );
}

This hook can only be called if you registered your extension with render, as that callback wraps the application in the necessary React context to make the input available anywhere in the tree.