is there a less intrusive way?
Hey @retohoehener, sorry to hear this. You can pass the env variable
EXPO_NO_TYPESCRIPT_SETUP=1 to the
expo start command to prevent this from happening. Would probably be worth creating an alias to avoid having to remember to pass it each time you run expo start.
Thank you @adamjnav. I solved this by manuall adding
Now expo doesn’t touch the file anymore.