Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yarn start no result: waiting for localhost .. #8273

Closed
CarpeDiemKopi opened this issue Oct 18, 2019 · 1 comment
Closed

yarn start no result: waiting for localhost .. #8273

CarpeDiemKopi opened this issue Oct 18, 2019 · 1 comment
Labels

Comments

@CarpeDiemKopi
Copy link

@CarpeDiemKopi CarpeDiemKopi commented Oct 18, 2019

I followed the instructions Getting Set Up exactly and it doesn't work.

image

And the instructions are confusing. Suddenly, firefox is mentioned, which has already been started and of which there was no talk before.

Step 4. Start the debugger

Now that Firefox is open, let’s start the development server. In a new terminal tab, run these commands:

windows 10 64 bit 1903

D:\TiddlyWiki\My_TiddlyWikis\git\debugger>yarn start
yarn run v1.19.1
$ node bin/dev-server
Listening for WS on localhost:8116, all traffic is proxied to localhost:6080
Protocol messages can be logged by enabling `logging.firefoxProxy` `in /configs/local.json`
Hot Reloading - https://github.com/firefox-devtools/debugger.html/blob/master/docs/local-development.md#hot-reloading
View debugger examples here:

https://github.com/firefox-devtools/debugger-examples
Development Server Listening at http://localhost:8000
 
webpack: Compiled successfully.
 

And yarn startalso messes with the internet connection.

@claim claim bot added the not-available label Oct 18, 2019
@loganfsmyth
Copy link
Contributor

@loganfsmyth loganfsmyth commented Jul 13, 2020

Support for developing the debugger as a standalone application has been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants