Bradley Ayers

I'm running into a similar problem when using yarn workspaces.

Hi @xavdid sure, here's the rough outline. ``` . ├── .gitignore ├── README.md ├── docker-compose.yml ├── tsconfig-base.json ├── tslint.json ├── node_modules ├── workspaces │   ├── app-lib │   │ ├── package.json...

Thanks. My plan is to just not support dependencies on sibling workspaces until then, and setup some package.json scripts that use `n use 8.10.0 ./node_modules/.bin/Zapier` prefix on Zapier commands. It’ll...

Another problem I've run into is `!Warning!! There is no .gitignore, so we are including all files. This might make the source.zip file too large`. I have a .gitignore in...

This happens on macOS too, in fact quite reliably after ~7 minutes and ~13,000 requests of hitting a HTTP server: Server: ``` $ python3 -mhttp.server 8015 ``` Client ([siege](https://github.com/JoeDog/siege/)): ```...

I dug a bit deeper into this and found what is happening. Under React strict mode, the same React element is being mounted and unmounted and then finally mounted again...

Here's an updated patch for 4.0.1: [react-native-reanimated-npm-4.0.1-40ff4579cd.patch](https://github.com/user-attachments/files/21522189/react-native-reanimated-npm-4.0.1-40ff4579cd.patch)

@JonnyBurger I've raised #513 to fix this, but if you don't want to wait for that you can patch your local extension code by inserting the following line where I...

@TomONeill if you're using TypeScript, and project references (in tsconfig.json files), make sure all the project references are paths to tsconfig.json (rather than directories). This works around the issue.

Are you able to share the tsconfig and directory/file structure? In my case this error came from it not being able to find the tsconfig.json for a given file, so...