Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Bug Report: `children` type missing when using components import with Strict ABI

Ouverte
  • Quelque chose ne va pas ?
#259 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
react-native, typescript
Domaine
frontend

Piste de recherche

Start with the react-native-css/components entry point, where View is re-exported with a className prop, and check how its props type is built from React Native's ViewProps. Reproduce by enabling Strict ABI in a small Expo app and running tsc on the ExpoView usage in app/index.tsx. Done when children type-checks on the wrapped component without TS2322, and the fix is clear about whether it belongs in the library's types or in the Strict ABI type setup.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

deferred (post-5.0)

Repository: my-expo-app

Describe the bug

When using React Native Strict/Standard ABI together with react-native-css, importing components from:

import { View as ExpoView } from 'react-native-css/components';

results in a TypeScript error because children is not included in the type definition.

Additionally, Strict ABI updates the types of all React Native components in the project itself, but it does not update the types inside the react-native-css library, which creates a mismatch between project components and library components.

Error message
app/index.tsx:12:6 - error TS2322: Type '{ children: Element; style: { flex: number; alignItems: "center"; padding: number; }; className: string; }' is not assignable to type 'IntrinsicAttributes & ViewProps & { className?: string | undefined; }'.
  Property 'children' does not exist on type 'IntrinsicAttributes & ViewProps & { className?: string | undefined; }'.

12     <ExpoView style={styles.container} className="bg-red-200">
        ~~~~~~~~
Reproduction
Expected behavior

ExpoView (and other components from react-native-css/components) should behave like normal React Native components extended with { className?: string }, meaning they should support children out of the box.

Actual behavior
  • Types are missing children.
  • Project components get updated types from Strict ABI, but the library components keep outdated types, leading to incompatibility.
Additional context
  • The issue happens only with Strict/Standard ABI enabled.
  • Without Strict ABI, the app compiles successfully.
  • Using styled(RNView) directly works fine.
  • Not sure if the fundamental fix should come from react-native-css directly or through additional adjustments in Strict ABI support.
Langage dominant
TypeScript
Étoiles
166
Forks
45
Merge moyen
13 j 14 h
PR mergées (30 j)
1

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nativewind/react-native-css

Toutes les issues de nativewind/react-native-css

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.