Lasse Peters

I'd be interested in this feature. What is the state here? Are there plans to merge it? Or should this go into a standalone package?

Technically, this kind of `default_exec_file` could also be executed as part of an "integration test" for this repo by the CI.

Sorry, that formulation was probably a bit cryptic. What I meant to suggest is to make use of the `precompile_executiojn_file` keyword argument of `PackageCompiler.create_sysimage`. You can find an example of...

I'm not sure how one can programmatically trigger the LanguageServer actions (though of course it should be possible). For the `JuliaFormatter` component, for example, you can just run `JuliaFormatter.format(".")` to...

Maybe it would also be possible to just execution the integration/unit tests of LanguageServer.jl to generate the precompile statements.

This is probably a good question to ask the VS code folks over at the Julia Slack channel. I think they should already have this kind of workflow for the...

I briefly talked to Sebastian from the LanguageServer.jl team and he says they don't ship a system image (or build on by default) because of the size restrictions in the...

The current Manifest is generated with Julia 1.7 and you are using Julia 1.6. One way to fix this is to download julia 1.7 and point the language server to...

I think one of the issues about the current approach that includes the `Manifest.toml` is that it makes an implicit assumption about the Julia version. Thus, including the Manifest in...

One possible alternative would be to have a Manifest per Julia version and the plugin would have to select the correct environment based on the julia version. That however seems...