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
Volar intellisense takeover mode does not resolve external workspaces/packages (monorepo) #19
Labels
enhancement
New feature or request
Comments
@johnsoncodehk I'm unfamiliar with where the module resolution for intellisense takes place. This doesn't appear to be due to project references as disabling this, see |
I can reproduce the same behaviour with TypeScript language server with |
blake-newman
added a commit
to blake-newman/volar.js
that referenced
this issue
Mar 20, 2023
Enable auto import by creating a real TS project and project service proxing the project methods to the languageServerHost. As we use a real project behind the scenes the language host no longer needs the auto import cache package to decorate as the project itself provides the module specifier and import caching behaviour. fixes: volarjs#19 fixes: vuejs/language-tools/issues#963 fixes: vuejs/language-tools/issues#1738
blake-newman
added a commit
to blake-newman/volar.js
that referenced
this issue
Mar 20, 2023
Enable auto import by creating a real TS project and project service proxing the project methods to the languageServerHost. As we use a real project behind the scenes the language host no longer needs the auto import cache package to decorate as the project itself provides the module specifier and import caching behaviour. fixes: volarjs#19 fixes: vuejs/language-tools#963 fixes: vuejs/language-tools#1738
blake-newman
added a commit
to blake-newman/volar.js
that referenced
this issue
Mar 22, 2023
Enable auto import by creating a real TS project and project service proxing the project methods to the languageServerHost. As we use a real project behind the scenes the language host no longer needs the auto import cache package to decorate as the project itself provides the module specifier and import caching behaviour. fixes: volarjs#19 fixes: vuejs/language-tools#963 fixes: vuejs/language-tools#1738
blake-newman
added a commit
to blake-newman/volar.js
that referenced
this issue
Mar 22, 2023
Enable auto import by creating a real TS project and project service proxing the project methods to the languageServerHost. As we use a real project behind the scenes the language host no longer needs the auto import cache package to decorate as the project itself provides the module specifier and import caching behaviour. fixes: volarjs#19 fixes: vuejs/language-tools#963 fixes: vuejs/language-tools#1738
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Volar is not handling resolving external workspaces/packages within monorepo.
Reproduction: https://github.com/blake-newman/vue-tsc-import-resolution
takeover mode: off
When takeover mode is off it is able to auto import the modules/dependencies from external workspaces/packages
./packages/main/src/index.ts
try to useisFalse
function fromb
package.takeover mode: on
When takeover mode is on it is unable to auto import modules/dependencies from external workspaces/packages
./packages/main/src/index.ts
try to useisFalse
function fromb
package.The text was updated successfully, but these errors were encountered: