I am working on a package locally and it seems like VSCode + LangServer don’t recognize the references to the package and it’s exported methods. For example: using TestPackage using CSV using DataFrames using BenchmarkTools using TestPackage.SomeModule: update! Here TestPackage and all the refere…

Sometimes adding a line like: if false; include("../src/flightpathcontroller.jl"); end helps…

Try this GitHub - PetrKryslUCSD/VSCode_Julia_portable: Portable Julia running in VSCode , perhaps?

Another option, let’s say your project structure is something like: TestPackage/ src/ TestPackage.jl foobar.jl examples/ basic_example.jl another_example.jl If you want intellisense to work insde examples/ you can create another environment inside that folder and dev’…

Related topic: [image] For which packages does VSCode autocomplete work? VS Code Let’s say I’m developing a package called MyPackage and I have activated its Project.toml. It has one dependency called MyDependency, and one test depency called MyTestDependency. After some …

[image] ufechner7: if false; include("../src/flightpathcontroller.jl"); end Seems like most solutions revolve around this. I tried that and it doesn’t work for me using TestItemRunner.jl not native tests, which is the required package to run tests in VSCode (althought its broken on its own). …

[image] feribg: this has to be a bug There are 51 open bugs on this topic: Issues · julia-vscode/julia-vscode · GitHub Just run your tests from the package manager using the test command… Don’t rely too much on VSCode…

Thanks for your workaround. I just realize that the environment of the REPL and the environment of VS Code window can be different.

Sorry to bring this up again, I also faced this problem. The workaround of @dylanxyz worked but I wonder is this a bug or at least there could be more correct way to fix this issue.

[image] SonLe: more correct way to fix this issue Try if GitHub - aviatesk/JETLS.jl: A new language server for Julia, enabling modern, compiler-powered tooling. fixes this for you.

I can confirm JETLS is helpful for this problem. It is sometimes laggy and warns some wrong errors but I think that’s ok due to still being in development process

VSCode and LangServer don't recognize local package

Tooling VS Code

gdalle May 2, 2024, 6:04am 5

Topic		Replies	Views
VS Code Intellisense for custom package New to Julia package , vscode	5	1003	March 23, 2021
Julia Language Server (VS Code Julia Extension) "missing reference" New to Julia question	9	580	December 8, 2024
For which packages does VSCode autocomplete work? VS Code intellisense , autocomplete	48	3413	December 5, 2025
Intellisense not working for dev'd package VS Code languageserver , intellisense	1	465	August 9, 2022
Tooling for VSCode / LSP VS Code vscode , languageserver	18	1147	October 17, 2024

VSCode and LangServer don't recognize local package

Related topics