tamagui / starter-free Goto Github PK

I'm going through the source code and trying to understand how this is all setup and one of the questions i have is why the aliases on expo are made on the babel.config file as opposed to on the tsconfig file?

hey, I'm using this starter for my project and I am trying to understand what's the best way to set up the backend with each platform.

for more clarification:
for nextjs they (nhost) have: @nhost/nextjs
and for react thay have the regular @nhost/react

and also in the provider configuration there is a difference:
as you can see here: https://docs.nhost.io/reference/docgen/react/types/nhost-react-client-constructor-params

...
clientStorage optional ClientStorage

Object where the refresh token will be persisted and read locally.

Recommended values:

'web' and 'cookies': no value is required
'react-native': import Storage from @react-native-async-storage/async-storage
'cookies': localStorage
'custom': an object that defines the following methods:
setItem or setItemAsync
getItem or getItemAsync
removeItem
'capacitor': import { Storage } from @capacitor/storage
'expo-secure-store': import * as SecureStore from 'expo-secure-store'
...

I want to be able to set up the provider for each platform in the proper way.
Now I'm trying to understand where I need to set this up?!

inside the packages/app/provider,
or inside each project

• apps/next/pages/_app.tsx
• apps/expo/app/_layout.tsx

anyhow, will be much appreciated.
thank you all

Current Behavior :
After upgrading to Expo SDK 51, the project fails to compile with the error TypeError: Cannot read properties of undefined (reading 'NativeModule').

Expected Behavior :
The project should compile without errors and work correctly with Expo SDK 51.

Tamagui Version:
1.98.0

Platform :
Web

Reproduction :

1. Clone the Tamagui starter from the latest version.
2. Update Expo to version 51.0.0 in the package.json file.
3. Run npm install or yarn install to update dependencies.
4. Start the project with yarn web.

OR

You can clone my test repository to reproduce the issue: Test Repository.

https://docs.google.com/spreadsheets/d/1FCPPiSSsE1KoeAkV8tVxmLe4iuNZI1PcCnMRaQUJZcM/edit?usp=drivesdk
Instincts' 24 schedule.pdf

Hi, I couldn't find a discussion tab so asking here, not an issue really. How are the react-native packages working on the NextJS app side?

For example, react-native-reanimated works as expected when I add an example on the NextJS app. However, when I tried to do this on my project, which is based on the Plasmo framework, I get errors as follows

Expected ',', got '{'
🟡 13     | ../plasmo/examples/with-react-native/node_modules/react-native/Libraries/Renderer/shims/ReactFabric.js:17:13

which forces me to add an alias key in the package.json. I had a similar error with using the moti library, which works on your starter kit. How have you done this? Thanks for your help!

Error seems to be with @types/react but it should refer from app directory. Please help

why not have it always latest versions of Expo and Next? also for next I think the app directory nav is the way to go instead of pages..... just thoughts