using the dagger vscode extension with cue lsp | Dagger | Page 1

limber scaffold Feb 28, 2023, 9:57 PM

#

Hi, how can one use the cue lsp these days? Also is this project still maintained, github.com/dagger/cuelsp?
I have installed the lsp server via go install github.com/dagger/cuelsp/cmd/cuelsp@latest but the vscode extension errors

[Error - 10:53:35 PM] dagger language server client: couldn't create connection to server.
Launching server using command dagger failed. Error: spawn dagger ENOENT

limber scaffold Feb 28, 2023, 11:04 PM

#

using the dagger vscode extension with cue lsp

ivory halo Mar 2, 2023, 3:15 PM

#

@fringe wren any advice?

ivory halo Mar 2, 2023, 6:10 PM

#

@limber scaffold Since we changed the name of the CUE-based Dagger binary to dagger-cue, we need to update the VS Code Extension to look for that instead of dagger.

I just tested a workaround with a symlink that works for me 🙂

I installed dagger-cue: https://docs.dagger.io/sdk/cue/526369/install
and then made this symlink

sudo ln -s `which dagger-cue` /usr/local/bin/dagger

Installation | Dagger

{@include: ../../../partials/_install-sdk-cue.md}

#

Now things are working for me.

limber scaffold Mar 2, 2023, 7:18 PM

#

oh nice. thanks.

#

seems like the cue related stuff doesnt get much love anymore. I personally would opt for go sdk most the time anyway but I am still wondering what the plans are regarding cue. Will it be removed completely at some point? What is the reason it appears barely used anymore? I see in the docs it says

a fan of the CUE language, and don't mind using the old Dagger engine
here: https://docs.dagger.io/

jade hamlet Mar 2, 2023, 7:50 PM

#

@limber scaffold more context here: #general message

#using the dagger vscode extension with cue lsp