katontech

I tried `expo start` in admin console and it crashed with the exact same error message. As a development user, my account has full permissions on the `' \ table.xsl.tmp'`...

I found that the new project created by `expo init` with [email protected] does not reproduce the symptoms. So, after deleting the `node_modules` of the project where the problem occurred and...

Unfortunately, it happened again in my project. On the other hand, it has not been reproduced yet in the project that only did `expo init` with [email protected].

Follow-up: Even in the project that just did `expo init` with [email protected], the symptom was reproduced about 1 hour after starting the connection with the device. Then restart the bundler...

This symptom is reproduced in the project created by [email protected] `expo init`, but the frequency is obviously lower than before. I have a project that is stable for more than...

I also occasionally see an error that `lstat` fails when accessing `node_modules\.bin`, but it doesn't continue. Rather than a static permission setting issue, maybe other processing for `node_modules` was happening...

It is interesting that the phenomenon involving the same file `table.xsl.tmp` as in my environment also occurred in another environment. I've also run into the fact that it doesn't reappear...

I don't even know that. I also searched for the installed expo-cli code and know that `table.xsl.tmp` is not directly referenced. Since expo-cli seems to work using various external tools,...

`table.xsl.tmp` is also a mystery to me. Naturally, I searched for `table.xsl. *` Somewhere on my PC, but I couldn't find it. I was wondering if it was a phenomenon...