---
title: "Comment by StackShortlist on \"Setting Up Claude Code So It Actually Writes Good React Native Code\" | Hashnode"
description: "The npx expo install versus npm install point deserves to be near the top, since a mismatched reanimated or gesture handler version is the most common way an Ex"
url: "https://hashnode.com/posts/claude-code-expo-react-native-setup/6ad22b4872e119bfdd270f9c/comment/6ad2aa0ba305ffe66917f809"
---

[Discussion](https://hashnode.com/posts/claude-code-expo-react-native-setup/6ad22b4872e119bfdd270f9c)

Comment [Setting Up Claude Code So It Actually Writes Good React Native Code](https://hashnode.com/posts/claude-code-expo-react-native-setup/6ad22b4872e119bfdd270f9c)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/claude-code-expo-react-native-setup/6ad22b4872e119bfdd270f9c/comment/6ad2aa0ba305ffe66917f809)

The npx expo install versus npm install point deserves to be near the top, since a mismatched reanimated or gesture handler version is the most common way an Expo app breaks after a dependency change. Adding a rule to run npx expo-doctor after any package change catches those mismatches before the next build. It is also worth listing which packages need a dev client rebuild, so nobody wastes time debugging Expo Go.