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

VTI Error: Cannot find module #1732

Closed
3 tasks done
odanado opened this issue Feb 25, 2020 · 8 comments · Fixed by #1752
Closed
3 tasks done

VTI Error: Cannot find module #1732

odanado opened this issue Feb 25, 2020 · 8 comments · Fixed by #1752

Comments

@odanado
Copy link
Contributor

odanado commented Feb 25, 2020

  • I have searched through existing issues
  • I have read through docs
  • I have read FAQ

Info

  • Platform: Linux
  • Node: 12.14.0
  • vti: 0.0.2

Problem

I get an error when I run vti.
Error: Cannot find module 'vscode-css-languageservice/lib/umd/data/browsers'

Reproducible Case

reproduction repository: https://github.com/odan-sandbox/vti-error-reproduction

@ApplicationDeveloper
Copy link

try this fix #1730

@ghost
Copy link

ghost commented Feb 26, 2020

try this fix #1730

Tried this fix, but it isn't working for me. I get almost the same error Error: Cannot find module 'vscode-css-languageservice/lib/umd/data/webCustomData'

@odanado
Copy link
Contributor Author

odanado commented Feb 26, 2020

Thanks!

I checked a version of vscode-css-languageservice. As a result of the version is 4.1.0.

$ yarn why vscode-css-languageservice
=> Found "vscode-css-languageservice@4.1.0"
info Reasons this module exists
   - "vti#vue-language-server" depends on it
   - Hoisted from "vti#vue-language-server#vscode-css-languageservice"

When I fixed to 4.0.2 a version of vscode-css-languageservice, vti command was succeeded.
https://github.com/odan-sandbox/vti-error-reproduction/pull/1/files

@selfagency
Copy link

I'm having this issue too.

This was referenced Feb 27, 2020
@octref octref added this to the February 2020 milestone Mar 3, 2020
@weilbith
Copy link

When is the next release planned to include this fix?

@selfagency
Copy link

@weilbith I'm no longer having this issue myself so I believe it's been fixed.

@weilbith
Copy link

weilbith commented May 20, 2020

Hmm I still have. So could only solve it by manually downgrading the vscode... dependency locally.
The linked fix was merged to master in march, while the latest npm release was 4 months ago.

@badbabykosh
Copy link

This is still a problem

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

Successfully merging a pull request may close this issue.

6 participants