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

relay-rsc

v0.0.4

Published

## Overview

Downloads

28

Readme

Relay-RSC Project

Overview

Relay-RSC is an early-stage alpha library developed to integrate Relay with React Server Components.

Key Features

  • Fragment Suspension Support: Allows fragments in components to suspend, offering improved control over data loading and rendering.
  • Alpha Stage Development: Being in its initial development phase, the project is open to contributions and suggestions for enhancements.

RSC Only

Currently the library only supports React Server Components. Serializing parts of the relay-component tree to be rendered on the server/client is not supported. Client components work as long as they don't receive any relay data from the RSC environment. In the future, we plan to add support for serializing the relay-component tree.

Installation

npm install relay-rsc
# or
yarn add relay-rsc

Usage

import { readQuery } from "relay-rsc";

async function HomePage() {
  const data = await readQuery(
    graphql`
      query HomePageQuery {
        viewer {
          id
          ...HomeFragment
        }
      }
    `,
    {},
    getCurrentEnvironment()
  );
  return (
    <div>
      Viewer {data.viewer.id}
      <Home viewer={data.viewer} />
    </div>
  );
}

async function Home(props) {
  const data = await readFragment(
    graphql`
      fragment HomeFragment on Viewer {
        id
      }
    `,
    props.viewer,
    getCurrentEnvironment()
  );

  return <div>Home {data.id}</div>;
}

Providing The Relay Environment

You need a way to provide the Relay Environment to the library. You can do this like the following example:

Note that the getCurrentEnvironment function is cached using react/cache to ensure that the same environment is used across the entire application.

import { Environment, Network, RecordSource, Store } from "relay-runtime";
import { cache } from "react";

const BACKEND_URL = process.env.BACKEND_URL;
export const getCurrentEnvironment = cache(function getCurrentEnvironment() {
  const store = new Store(new RecordSource());
  const network = Network.create(async ({ id, name, text }, variables) => {
    if (!BACKEND_URL) throw new Error("BACKEND_URL is not set");
    const response = await fetch(BACKEND_URL, {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
      },
      body: JSON.stringify({
        query: id ?? text,
        variables,
      }),
    });

    const json = await response.json();
    return json;
  });
  return new Environment({
    network,
    store,
    isServer: false,
  });
});