Thomas Pischulski
Thomas Pischulski
Any updates on this?
@gusflopes create a `.vscode/settings.json` in your repo and paste it there
Running into the same issue when adding subtitles (`.vtt` files) to the asset library and using them in bloks. Video files work fine
What helped me in my npm monorepo: 1. `npm uninstall` all `swc` related packages 2. remove `package-lock.json` 3. remove all `node_modules` directories 4. `npm install` 5. `npm install` the `swc`...
But `$mono` is a pre defined tamagui token. Shouldn't it already be included then?
@tech-chieftain one approach on how to have a client per tenant is linked in the OP > https://darioielardi.dev/schema-based-multi-tenancy-with-nestjs-and-prisma
Yup just checked it with most recent tamagui version yesterday
@natew can you point me into the right direction? EDIT: If you meant `@tamagui/metro-plugin` like explained here https://tamagui.dev/docs/guides/expo then yes it still happens on tamagui's input elements
Exactly I needed to keep clicking on the input to be able to type. Will set up a repo to reproduce it later
@natew I found that the issue was on my end sorry, it was related to having the input within `KeyboardAvoidingView` and `TouchableWithoutFeedback`: ```tsx ``` Feel free to close the issue