-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Vue UI not launching #3700
Comments
Forced to refresh the browser should be fine. |
Refreshing the browser does not fix this. Using another browser (Firefox or GNOME web) on my Arch Linux system works fine. If I use the path http://localhost:8000/project/select that also works fine in Chrome. I see these errors in my console https://imgur.com/a/XyJUq9D. Both JS files contain HTML. I am using vue-cli 3.5.4. I just starting trying out Vue and UI in the last few days. This and another basic issue #3664 are very disappointing :( |
@bulletmark The GUI is still in beta, if you want the stable experience use the CLI in the terminal. |
There must be a bug somewhere because vue ui is not working after installing everything from scratch node.js (10.16.3 LTS), npm and @vue/cli. Firefox shows this error: Chrome shows this error: Do you have any idea why the SSL of the ui could be broken? |
Updated from 10.15.1 to 10.16.3. |
Unfortunately now building the project doesn't work anymore and throws out other errors |
Version
Environment info
Steps to reproduce
run 'vue ui' from terminal
What is expected?
Vue UI tool is started and launched automatically on http://localhost:8000
What is actually happening?
Terminal reports:
New tab is launched in Chrome, but nothing is displayed.
Recently updated from version 3.3.0. Was having previously noted issue where using Vue UI tool would fail to build new projects correctly with that version. Have attempted npm uninstall/reinstall of vue and @vue/cli with same results.
Additional Note: Receive following warning when running npm install -g @vue/cli:
Suggest updating dependency to require
cross-spawn
in npm config to ensure newer package is used.The text was updated successfully, but these errors were encountered: