SafeAreaView is re-exported unwrapped from the safe-area-context shim: className silently no-ops (breaks flex-1 screen roots after v4 -> v5 migration)

[Thomas-athletics]

Summary

The react-native-safe-area-context shim wraps SafeAreaProvider (to expose the inset CSS variables) but re-exports everything else from the original package unwrapped:

// src/components/react-native-safe-area-context.native.tsx
export * from "react-native-safe-area-context";

export function SafeAreaProvider({ children, ...props }: SafeAreaProviderProps) { ... }

SafeAreaView is therefore the original component, and className on it is a silent no-op — no warning, no error.

Why this is painful

<SafeAreaView className="flex-1 ..."> is an extremely common screen-root pattern in NativeWind v4 apps (the v4 JSX transform made it work on any component). After migrating to NativeWind v5 / react-native-css, every such screen root silently loses flex: 1, the SafeAreaView collapses to content height, and ScrollViews inside shrink to zero — the entire screen body renders blank while headers/tab bars (styled via style objects) keep working.

Nothing catches it statically: tsc, jest, and expo export are all green (the CSS compiles fine; it just never reaches the component). We only found it via on-simulator UAT. In our app it affected 44 SafeAreaView className call sites, i.e. every screen.

Environment

• react-native-css 3.0.7, nativewind 5.0.0-preview.4, tailwindcss 4.3.3
• Expo SDK 57, React Native 0.86, New Architecture enabled, pnpm monorepo (hoisted)
• Metro via withNativewind(config, { inlineVariables: false }), default globalClassNamePolyfill (true)

Repro

import { SafeAreaView } from "react-native-safe-area-context";

export default function Screen() {
  return (
    <SafeAreaView className="flex-1 bg-red-500">
      <Text>never gets a red full-height background</Text>
    </SafeAreaView>
  );
}

<View className="flex-1 bg-red-500"> in the same tree styles correctly, confirming the CSS pipeline itself works.

Suggested fix

Wrap SafeAreaView in the shim like the other intercepted components, e.g.:

import { SafeAreaView as OriginalSafeAreaView } from "react-native-safe-area-context";
import { useCssElement } from "react-native-css";

export function SafeAreaView(props: SafeAreaViewProps & { className?: string }) {
  return useCssElement(OriginalSafeAreaView, props, { className: "style" });
}

We are currently shipping exactly that as a local pnpm patch on dist/ (module + commonjs) and it fully restores v4 behavior — all screens render identically to our NativeWind 4 baseline.

More generally: a dev-mode warning when className is passed to a component that nothing intercepts would have turned a multi-hour debugging session into a one-line console message. Happy to open a PR for the SafeAreaView wrap if useful.

[github-actions]

🤖 Auto-triage

Status: CONFIRMED
Type: bug
Version: v5

Findings

Confirmed by code inspection. src/components/react-native-safe-area-context.native.tsx:13 does a blanket export * from "react-native-safe-area-context", which re-exports the original SafeAreaView unwrapped. Only SafeAreaProvider is intercepted (to expose the inset CSS variables). Since SafeAreaView is not routed through useCssElement like View at src/components/View.tsx:15-20, a className prop on it is a silent no-op — the CSS compiles fine but never reaches the component.

What I tested

• Read src/components/react-native-safe-area-context.native.tsx — confirms export * pattern and only SafeAreaProvider is wrapped.
• Read src/components/View.tsx — confirms the expected wrapping pattern using useCssElement(RNView, props, { className: "style" }).
• Read src/components/react-native-safe-area-context.tsx (web) — also just export * from "react-native-safe-area-context".
• Reviewed the directory listing at src/components/ — no SafeAreaView.tsx or equivalent wrapper exists.

Next steps

• The reporter's suggested fix is on-brand and matches the existing View.tsx pattern; wrap SafeAreaView (and likely SafeAreaInsetsContext/SafeAreaFrameContext consumers are fine as-is) via useCssElement in react-native-safe-area-context.native.tsx. The web shim (react-native-safe-area-context.tsx) may also need the same wrap since RN Web renders SafeAreaView as a View.
• Consider the reporter's secondary ask: a dev-mode warning when className is passed to a component nothing intercepts. This would materially improve DX for v4→v5 migrations.
• Accept the offered PR if bandwidth allows.

---

_{This is an automated triage. See auto-triage.yml.}