Version

3.0.3

Node and OS info

node v10.11.0 / yarn 1.94 / Linux Mint 18.3 Sylvia

Steps to reproduce

$ vue ui
or
$ vue ui -D
or
$ vue ui --headless -D

What is expected?

In normal cases, the port and address would be generated and I could consequently access the portal that would permit me to add, create or edit vue projects in lieu of "vue create" for version 3 projects or "vue init" for version 2 projects.

What is actually happening?

################

vue ui will not launch in either Chrome or Firefox (latest releases). The vague errors are visible in the developer tools and not in the terminal/Bash application.

For example, in Firefox Devtools I see the following:

Firefox can’t establish a connection to the server at ws://localhost:8000/graphql. ( client.js:426 )

In Chromium devtools, I see this:

Network error: Cannot use GraphQLSchema "[object Object]" from another module or realm. ( vue-apollo.js:56 )
Ensure that there is only one instance of "graphql" in the node_modules (etc., etc.)

But it is only after I HOVER over the line description (client.js:426) in Firefox that I am able to make a lick of sense at all out of the situation. If I am not mistaken, I think the WEBSOCKET ADDRESS ws://localhost:8000/graphql is pointing to on one of your contributor's workstation (Soda).

The generated hover-text reveals "webpack:///Users/soda/Projects/vue-cli/node_modules/subscriptions-transport-ws/dist/client.js:426" and not an address that is relative to MY OWN local instance of webpack.

In chrome, the error proposes a solution (as it relates to ApolloError.js:46) to the effect of:

a) Ensure that there is only one instance of "graphql" in the node_modules directory. If different versions of "graphql" are the dependencies of other relied on modules, use "resolutions" to ensure only one version is installed.

Then, suggests that I should visit [ https://yarnpkg.com/en/docs/selective-version-resolutions ]

...and it offers, b) a canned explanation to the effect of: "Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results."

In sum, the issue is with the reference to the Websocket address and how it presently points to "webpack:///Users/soda/Projects/vue-cli/node_modules/subscriptions-transport-ws/dist/client.js:426".

I strongly believe that I should not have to make exceptions in my browser (whether Firefox or Chromium) to permit web-socket addresses from (excuse the expression) "spurious" sources in the about:config settings.

Push a new minor version as soon as possible. I would love to work with vue ui on Linux. I thank you in advance for your prompt attention to this matter.

Cordially,

Luis Artavia \
Heredia, Costa Rica \
Front-end Web Developer Extraordinaire \

################