Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expo/Metro - Unable to resolve ".tamagui/css/apptabslayouttsx.css" #2538

Open
febLey opened this issue Apr 16, 2024 · 3 comments
Open

Expo/Metro - Unable to resolve ".tamagui/css/apptabslayouttsx.css" #2538

febLey opened this issue Apr 16, 2024 · 3 comments

Comments

@febLey
Copy link

febLey commented Apr 16, 2024

Current Behavior

When the .tamagui folder is being deleted or isn't present because of the gitignore file, tamagui is unable to recreate the css folder with it's contents, which causes the metro build to fail.

Expected Behavior

Tamagui should recreate the .tamagui folder with all of it's contents and metro should be able to launch via the npm run web command

Tamagui Version

1.94.5

Platform (Web, iOS, Android)

Web

Reproduction

npm create tamagui@latest --template issue2538

Select: Expo Router (beta)

cd issue2538
npm run web

After the build is complete and the page is being displayed in the browser: Ctrl + c

rm -rf .tamagui
npm run web

System Info

System:
    OS: macOS 14.3.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 2.68 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    Yarn: 4.0.2 - ~/.nvm/versions/node/v20.11.0/bin/yarn
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
    bun: 1.0.2 - ~/.bun/bin/bun
    Watchman: 2024.03.25.00 - /usr/local/bin/watchman
  Browsers:
    Chrome: 123.0.6312.124
    Safari: 17.3.1
    Safari Technology Preview: 17.4
  npmPackages:
    @babel/core: ^7.23.3 => 7.23.7
    @expo/metro-runtime: ~3.1.3 => 3.1.3
    @react-navigation/native: ^6.0.2 => 6.1.9
    @tamagui/config: ^1.94.5 => 1.94.5
    @tamagui/metro-plugin: ^1.94.5 => 1.94.5
    @types/react: ~18.2.14 => 18.2.47
    babel-preset-expo: ^10.0.1 => 10.0.1
    expo: ~50.0.6 => 50.0.6
    expo-font: ~11.10.2 => 11.10.2
    expo-linking: ~6.2.1 => 6.2.2
    expo-router: ~3.4.7 => 3.4.7
    expo-splash-screen: ~0.26.4 => 0.26.4
    expo-status-bar: ~1.11.1 => 1.11.1
    expo-system-ui: ~2.9.3 => 2.9.3
    expo-web-browser: ~12.8.2 => 12.8.2
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    react-helmet-async: ~2.0.4 => 2.0.4
    react-native: 0.73.4 => 0.73.4
    react-native-reanimated: ~3.6.2 => 3.6.2
    react-native-safe-area-context: 4.8.2 => 4.8.2
    react-native-screens: ~3.29.0 => 3.29.0
    react-native-web: ^0.19.10 => 0.19.10
    tamagui: ^1.94.5 => 1.94.5
    typescript: ^5.3.3 => 5.3.3
@febLey
Copy link
Author

febLey commented Apr 16, 2024

I reproduced it on a separate macOS system (14.4.1).
Interestingly enough I can get it to build the css files, when I restart the PC.

But the think might be related to this issue: #2230

@ehxxn
Copy link
Member

ehxxn commented Apr 16, 2024

is it happening on Windows ?

@febLey
Copy link
Author

febLey commented Apr 18, 2024

Unfortunately I don't have a Windows workspace, but I will try to reproduce it under Linux.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants