Replies: 3 comments 7 replies
-
Automatically opening the browser is intentionally turned off via |
Beta Was this translation helpful? Give feedback.
-
I think you mean But anyway, in the readme, you have:
This command will open http://localhost:9090 in your browser with live reload, allowing you to see the changes as you develop. That's not the main issue. I did pass a custom port as mentioned above, the result was the same: typing http://localhost:XXXX into the browser with any port I set fails with "connection refused". If I remove --no-browser from the "serve" script in package.json, the result is also the same. |
Beta Was this translation helpful? Give feedback.
-
Thanks, that does fire up the live-server 👍 I still have the more problematic issue that the plugin examples will not load. This is the error: |
Beta Was this translation helpful? Give feedback.
-
I followed readme instructions. After 'yarn start' terminal logs:
No window is launched in the browser. http://localhost:9090 results in connection refused.
Using the VS Code Golive plugin, the example pages fire up correctly (using port 5500). I killed goLive and ran live-server on port 5500, to see if it was a port conflict on 9090, but it did not fix things.
With goLive plugin, many examples work (basic, options, bars, pre-decoded)
However:
Speed: Cannot read properties of null (reading 'addEventListener')
All plugin examples error with "Container not found". Except "Record". This errors with "Cannot set properties of null (setting 'onclick')"
In advanced section, gradient, split channels and custom render work. The others do not.
As I'd be interested in making sticky labels, the spectrogram plugin one is what I am most interested in getting working.
OS: Windows 11
Browser: Chrome (latest)
Beta Was this translation helpful? Give feedback.
All reactions