create-t3-turbo: bug: Unable to run `pnpm dev` in expo due to `.gitignore`

Provide environment information


  System:
    OS: Linux 6.5 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i9-12900HK
    Memory: 44.39 GB / 62.47 GB
    Container: Yes
    Shell: 3.3.1 - /usr/bin/fish
  Binaries:
    Node: 21.6.0 - ~/.local/share/nvm/v21.6.0/bin/node
    npm: 10.2.4 - ~/.local/share/nvm/v21.6.0/bin/npm
    pnpm: 8.11.0 - ~/.local/share/pnpm/pnpm

Describe the bug

Upon downloading the template, I’m unable to run pnpm dev in apps/expo. I receive the following permissions error due to the .gitignore:

Starting Metro Bundler
Error: EACCES: permission denied, open '/home/learning-projects/t3-test/apps/expo/.gitignore'
    at Object.readFileSync (node:fs:456:20)
    at Object.upsertGitIgnoreContents (/home/learning-projects/t3-test/node_modules/@expo/cli/src/utils/mergeGitIgnorePaths.ts:121:30)
    at Object.startTypescriptTypeGenerationAsync (/home/learning-projects/t3-test/node_modules/@expo/cli/src/start/server/type-generation/startTypescriptTypeGeneration.ts:51:85)

Link to reproduction

https://github.com/t3-oss/create-t3-turbo

To reproduce

npx create-turbo@latest -e https://github.com/t3-oss/create-t3-turbo

cd repo_name

pnpm i

cd apps/expo

pnpm dev

Additional information

No response

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 11
  • Comments: 23 (4 by maintainers)

Most upvoted comments

Hi, I had the same issue. It looks like the .gitignore file gets generated without any rwx permissions. I fixed the issue by deleting the file and creating an empty /apps/expo/.gitignore file. The file should get updated automatically once you run pnpm dev again.

I opened an issue right after expo started generating gitignore that got converted to discussion (see https://github.com/expo/router/discussions/846)

I bumped that to see if they want a new issue or not. Either way I think we can keep this issue open just for visibility until they have fixed it on there part.

I can confirm that this is not a unique T3 issue, I get the same in an NX monorepo

Does anyone know where to put this then? I feel like the proper steps are:

  1. Close this issue
  2. Make a note somewhere that there is a solution to the solution (namely, running chmod 644 apps/expo/.gitignore)
  3. Add a new issue in one of the expo-cli repos