running expo start with SDK 41 destroyed my carefully documented tsconfig.json

Expo Development Tools
1

is there a less intrusive way?

2

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.

Cheers,
Adam

3

Thank you @adamjnav. I solved this by manuall adding

"extends": "expo/tsconfig.base"

Now expo doesn’t touch the file anymore.

4

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.