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
https://github.com/butlerx/wetty/blob/main/docs/development.md does not make it clear what URL to open to access the locally-running server, and the yarn dev script actually attempts to xdg-open http://localhost:8080/ (some built-in default?) which is incorrect and confusing.
To Reproduce
Steps to reproduce the behavior:
Check out git src.
yarn
yarn build
yarn dev
Expected behavior
Once WeTTY is running locally, any one of the following happens:
the web UI is opened for me automatically by script, or
I follow clear and correct instructions on how to open it, either output by the script, or in the development.md docs.
yarn dev attempts to xdg-open http://localhost:8080/, i.e. the incorrect URL. Apparently something else is listening on this URL, but it's not serving WeTTY.
Additional context
Luckily I was able to figure out what I'm supposed to be doing was by parsing the [1] info: Starting server {"base":"/wetty/","label":"Wetty","port":3000,... log line, but it would be far better if new prospective devs faced fewer obstacles getting started.
The text was updated successfully, but these errors were encountered:
close issue #432
- use `snowpack build --watch` rather then `snowpack dev`
- Update `docs/developments.md` to reflect the acutal development
environment
Describe the bug
https://github.com/butlerx/wetty/blob/main/docs/development.md does not make it clear what URL to open to access the locally-running server, and the
yarn dev
script actually attempts to xdg-openhttp://localhost:8080/
(some built-in default?) which is incorrect and confusing.To Reproduce
Steps to reproduce the behavior:
yarn
yarn build
yarn dev
Expected behavior
Once WeTTY is running locally, any one of the following happens:
Actual behavior
Additional context
Luckily I was able to figure out what I'm supposed to be doing was by parsing the
[1] info: Starting server {"base":"/wetty/","label":"Wetty","port":3000,...
log line, but it would be far better if new prospective devs faced fewer obstacles getting started.The text was updated successfully, but these errors were encountered: