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

react-server-action

v0.2.15

Published

## Usage

Downloads

22

Readme

React Server

Usage

npm add react-server-action
yarn add react-server-action
pnpm add react-server-action
import { validate, reactServerAction } from 'react-server-action'

const isServerLayer = true
const result = validate('path/to/file', isServerLayer)
if (!result.error) {
  const code = await reactServerAction('path/to/file', '__prefix__', isServerLayer)
  console.log(code)
}

Collection of React Server tools

RSC rules

Valid RSC

'use server'
'use client'
// ❌
'use server'
// ✅
'use client'
// ✅
'use client'
export const foo = async () => {
  'use server'
  return 'rsc'
}
// ❌
export const foo = async () => {
  'use server'
  return 'rsc'
}
// ✅

Register RSC

Option 1: export __PREFIX__+name in the same file

import { registerServerReference } from 'react-server-dom-webpack/server'

export const foo = async () => {
  'use server'
  return 'rsc'
}

export const __prefix__foo = registerServerReference(foo, 'file_id', 'foo')

Option 2: register in local map

import { registerServerReference } from 'react-server-dom-webpack/server'

export const rscMap = new Map()

function register (
  fn: Function,
  file: string,
  name: string,
) {
  registerServerReference(fn, file, name)
  rscMap.set(id, fn)
  return fn
}

export const foo = async () => {
  'use server'
  return 'rsc'
}

register(foo, 'file_id', 'foo')

Transform RSC

Case 1: server action file

'use server'

export async function foo () {
  return 'rsc'
}

export function not_rsc () {
  return 'not_rsc'
}

⬇️

'use server'
import { registerServerReference } from 'react-server-dom-webpack/server'

export async function foo () {
  return 'rsc'
}

export function not_rsc () {
  return 'not_rsc'
}

export const __prefix__foo = registerServerReference(foo, 'file_id', 'foo')

Case 2: non-exported server action

async function wrapFn (...args: any[]) {
  'use server'
}

export const App = () => {
  wrapFn()
  return <div>App</div>
}

⬇️

import { registerServerReference } from 'react-server-dom-webpack/server'

async function wrapFn (...args: any[]) {
  'use server'
}

export const App = () => {
  wrapFn()
  return <div>App</div>
}

export const __prefix__wrapFn = registerServerReference(wrapFn, 'file_id', 'wrapFn')

Note that all server actions should be exported, otherwise server runtime cannot access them.

Case 3: server action in nested function

import { Component } from '@/components'

export const App = (props) => {
  const foo = async (input: string) => {
    'use server'
    return JSON.stringify(props) + input;
  }
  return <Component action={foo} />
}

⬇️

import { registerServerReference } from 'react-server-dom-webpack/server'
import { Component } from '@/components'

export const App = (props) => {
  const foo = __prefix__1.bind(null, [props])
  return <Component action={foo} />
}

export const __prefix__1 = registerServerReference(async (bound, input) => {
  'use server'
  const [props] = bound;
  return JSON.stringify(props) + input;
}, 'file_id', '__prefix__1')

You should save the context of the function correctly, otherwise the function will not work as expected.

Case 4: server action in jsx

export const App = (props) => {
  return <div onClick={async () => {
    'use server'
    console.log(props)
  }} />
}

⬇️

import { registerServerReference } from 'react-server-dom-webpack/server'

export const App = (props) => {
  return <div onClick={__prefix__action_1.bind(null, [props])} />
}

export const __prefix__action_1 = registerServerReference(async (bound) => {
  'use server'
  const [props] = bound
  console.log(props)
}, 'file_id', '__prefix__action_1')

LICENSE

MIT