You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
yarn run v1.22.11
$ expo start --web
Starting project at /tmp/src/etesync-notes
Unable to find expo in this project - have you run yarn / npm install yet?
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
note i've had yarn run successfully, as well as npm install (trying to follow the above error's expo hint)
possible lead: is it correct that the READMe says to have both yarn and npm installed?
tdl;dr maybe this is a "support" ticket (in which case, feel free to close it - i'm happy to try debugging live in the matrix room instead) but maybe something's off with the readme? wanna double-check before i investigate further
The text was updated successfully, but these errors were encountered:
I think the issue you are facing (and we should probably update the readme!) is that developing the web requires yarn add expo. We are however not adding this dep permanently because it adds non-free components to the Android and iOS bulids which we don't want.
Thanks, that worked and indeed I'm able to see the UI on localhost now.
I've started a pull request with the update to the readme you mention, and threw in a few other TODOs that might be helpful for me to figure out and include before I close that PR.
tasn
linked a pull request
Aug 2, 2021
that will
close
this issue
yarn web
results in:note i've had
yarn
run successfully, as well asnpm install
(trying to follow the above error's expo hint)possible lead: is it correct that the READMe says to have both yarn and npm installed?
tdl;dr maybe this is a "support" ticket (in which case, feel free to close it - i'm happy to try debugging live in the matrix room instead) but maybe something's off with the readme? wanna double-check before i investigate further
The text was updated successfully, but these errors were encountered: