Open ericdrobinson opened 3 years ago
Where is vue package? It isn't a regular monorepo.
The vue
package is installed in the top-level node_modules
folder. It is v2.6.11 with a patch applied.
I should also note that I found a path bug in the initial config while reviewing this issue. Fixing that path bug (don_html
→dom_html
) didn't fix the issue at all.
The Vue Language Server output still gets stuck at "Vetur initialized".
The only thing I can think at the moment is that perhaps vetur
is finding the tsconfig.json
files correctly but not following the inheritance to build the "full config"?
Oh, I should also mention that removing one of the projects
there so that it only sees, say, the one defined at dom_html/panel
ends with the same results...
If you can provide a minimal repro case, we can study quickly. https://github.com/vuejs/vetur/blob/master/.github/NO_REPRO_CASE.md
Vetur: Restart VLS
Info
vetur.config.js
contents:Problem
If the
vetur.config.js
file as shown above exists in the project root, Vetur features fail to activate. The Vue Language Server output does contain the following message:But that is all. No Vetur features beyond syntax highlighting appear to work.
If the contents of
vetur.config.js
are commented out, then the output shows:Enabling the Trace: Server setting to
verbose
in the extension settings shows lots of message traffic with, presumably, the extension host. I can clearly see hover requests show up but responses are always empty arrays.Reproducible Case
I do not yet have this information available. What I have found is that simply specifying one of the projects listed in the config shown above and leaving the
settings
out of it will result in this failure state. The moment that I comment out everything (effectively remove thevetur.config.js
file altogether), many features begin to work again (although some of the template interpolation warnings appear to skip some of the TypeScript type declarations).