Arnie
Arnie
Yes, it seems pretty awkward that at this point in time CRA still hasn't solved this issue. ``` Development ├── Common Framework │ └── tsconfig.json └── MyApp ├── NodeProject │...
> `path.normalize` Thank you very very much, this indeed fixed my issue.
### Confirming that it still doesn't work as expected | Property | Value | | --- | --- | | Electron | 19.0.4 and 19.0.5 | | OS Edition |...
bump On Fri, Oct 7, 2022, 10:20 PM github-actions[bot] ***@***.***> wrote: > This issue has been automatically marked as stale. *If this issue is > still affecting you, please leave...
Any updates on the issue?
I'm here to confirm that on my end of things this issue is still alive (`Dialog.Button`). Still triggering in this environment: ``` "dependencies": { "@expo/metro-runtime": "~4.0.1", "@gorhom/bottom-sheet": "^5.0.6", "@paralleldrive/cuid2": "^2.2.2",...
February 2nd, 2023: This is still an issue. On my side of the lake, the only value respected in the `.env` file is "none" (BROWSER=none). Any other value results in...
#3907 Same issue here.
@TsplayerT & @VitorNilson I'm afraid the current version--at this time obviously--doesn't contain `legacy`, so we won't be able to use that as a solution (expo-sqlite@~15.0.6 against typeorm@^0.3.20). On my end...
> [@ArnieGA](https://github.com/ArnieGA) Expo has a _very_ hard time using local npm packages; as a workaround, I created an npm package of the branch that contains the fix. See https://www.npmjs.com/package/@swiftdevil/typeorm. My...