types.d.ts doesn't type-check against React Native 0.88: Touchable, ScrollViewProps and VirtualizedListProps #548

Activity

1. YevheniiKotyrlo commented on Oct 30, 2026

   

   YevheniiKotyrlo

   on Oct 30, 2026

   ContributorAuthor

   More actions

   This is the patch I apply to the published 3.1.0-rc.0 until a fix lands: it keeps every added className property and drops the extends clauses along with the imports they used, which React Native 0.88's types reject.

   diff --git a/types.d.ts b/types.d.ts
   --- a/types.d.ts
   +++ b/types.d.ts
   @@ -1,11 +1,5 @@
    /* eslint-disable @typescript-eslint/no-unused-vars */
   -import type {
   -  ScrollViewProps,
   -  ScrollViewPropsAndroid,
   -  ScrollViewPropsIOS,
   -  Touchable,
   -  VirtualizedListProps,
   -} from "react-native";
   +import type { ScrollViewProps } from "react-native";
    
    declare module "@react-native/virtualized-lists" {
      export interface VirtualizedListWithoutRenderItemProps<ItemT>
   @@ -19,17 +13,13 @@ declare module "react-native" {
      interface ButtonProps {
        className?: string;
      }
   -  interface ScrollViewProps
   -    extends ViewProps,
   -      ScrollViewPropsIOS,
   -      ScrollViewPropsAndroid,
   -      Touchable {
   +  interface ScrollViewProps {
        contentContainerClassName?: string;
      }
   -  interface FlatListProps<ItemT> extends VirtualizedListProps<ItemT> {
   +  interface FlatListProps<ItemT> {
        columnWrapperClassName?: string;
      }
   -  interface ImageBackgroundProps extends ImagePropsBase {
   +  interface ImageBackgroundProps {
        imageClassName?: string;
      }
      interface ImagePropsBase {
   @@ -47,7 +37,7 @@ declare module "react-native" {
      interface TouchableWithoutFeedbackProps {
        className?: string;
      }
   -  interface KeyboardAvoidingViewProps extends ViewProps {
   +  interface KeyboardAvoidingViewProps {
        contentContainerClassName?: string;
      }
    }
2. dave-otf commented on Oct 31, 2026

   

   dave-otf

   on Oct 31, 2026

   More actions

   One diagnostic that may help separate the package augmentation from the app: run the repro once with skipLibCheck: true. If the declaration diagnostics disappear, that confirms the failure is in .d.ts checking; it is only a temporary isolation step, not a compatibility fix, and it does not validate runtime behavior. Then keep the skipLibCheck: false repro as the regression check for the eventual 0.88-compatible declarations.