why is the dev server generating .gitignore #846
Replies: 3 comments 3 replies
-
There's two reasons: The practical reason is that features are still experimental and they are not as strictly covered by semver. By forcing them to be inside a The stylist reason, I'm going to close this issue and move it to a discussion as I am interested in people's opinions on the subject. |
Beta Was this translation helpful? Give feedback.
-
Hey @marklawlor, It seems like this is now causing issues due to lack of permissions on windows (see t3-oss/create-t3-turbo#873). Any chance we can get an override option to skip generation? |
Beta Was this translation helpful? Give feedback.
-
Which package manager are you using? (Yarn is recommended)
pnpm (known issues due to Metro)
Summary
I enabled the experimental typedRoutes features and ever since expo router is generating a
.gitignore
everytime i run dev.I think it's kinda silly to generate this file multiple times, I tend to not have nested gitignores in my monorepos but just keep a general purpose one in root, so having expo-router generate one for me everytime i run dev is kinda annoying
I think it's fair to assume devs can put things in their gitignores themselves, and you don't have to generate it for us.
Minimal reproducible example
Happy to provide one if you deem necessary, for now just check out create-t3-turbo where i have the gitignore in root and don't want one in the expo directory
Beta Was this translation helpful? Give feedback.
All reactions