Bug: Server Components error when directly rendering a Context

[samselikoff]

A Server Component that renders <Context> directly will result in a runtime error:

Element type is invalid. Received a promise that resolves to: Context. Lazy element type must resolve to a class or function.

Here's the minimum repro:

import { Context } from './context';

export default function Home() {
  return <Context value={2}>hello</Context>;
}

// context.tsx
'use client';

import { createContext } from 'react';

export const Context = createContext(1);

React version: 19.3.0-canary-378973b3-20251205

Link to code example:

https://github.com/samselikoff/2025-12-09-render-context-from-rsc

The current behavior

Renders without error

The expected behavior

Errors with

Element type is invalid. Received a promise that resolves to: Context. Lazy element type must resolve to a class or function.

[sahilatahar]

I also tried to find out that you are getting this error because:

Your context file is a client component ('use client'), so a Server Component (page.tsx) cannot render it directly.

Correct code:

// context.tsx
"use client";
import { createContext } from "react";

export const Context = createContext(1);

export function ContextProvider({ children }: { children: React.ReactNode }) {
	return <Context value={2}>{children}</Context>;
}

// page.tsx
import { ContextProvider } from "./context";

export default function Home() {
	return <ContextProvider>hello</ContextProvider>;
}

[samselikoff]

@sahilatahar I believe <Context> should be renderable directly from an RSC (per a core team member). Believe it's a bug.