node\r: No such file or directory

[adelarsq]

Trying to initiate the server in the console on OSX shows an error:

→ docker-langserver --stdio
env: node\r: No such file or directory

Related issue nwutils/nw-builder#75

Update:
Solved with:

→ cd  ~/.config/yarn/global/node_modules/dockerfile-language-server-nodejs/bin
→ sudo dos2unix docker-langserver
dos2unix: converting file docker-langserver to Unix format...

[rcjsuen]

Thank you for the bug report, @adelarsq. Looks like the file uses \n for its newlines in the repository but I published it with \r\n when I cloned it on Windows because of my auto.crlf setting.

[rcjsuen]

@adelarsq This should be fixed in the new v0.0.12 release. Could you install it and give it a try?

[adelarsq]

@rcjsuen It's fixed. Thanks.

[zoedsoupe]

I have this same issue on Arch Linux with the latest version of docker-langserver

[Frederick888]

Can confirm. I fixed it locally for now. Perhaps set up CI/CD somewhere to publish new versions if @rcjsuen usually works under Windows?

[rcjsuen]

I have this same issue on Arch Linux with the latest version of docker-langserver

@Mdsp9070 Apologies for not responding to this earlier. Looks like it got lost in my notifications. I'm surprised that this is happening since the docker-langserver file hasn't been touched in a while. I ran npm install -g docker-langserver on macOS and did not experience any problems with 0.3.0. 🤔

[Frederick888]

@rcjsuen It seems npm does its magic converting CRLF to LF. If you use yarn global add dockerfile-language-server-nodejs instead, the entry script will have CRLF under Linux/macOS, rendering it unusable.

$ wget "$(npm view dockerfile-language-server-nodejs dist.tarball)"
$ tar xvf dockerfile-language-server-nodejs-0.3.0.tgz
$ uniname package/bin/docker-langserver | rg CR\|LF
No LINES variable in environment so unable to determine lines per page.
Using default of 24.
       19         19  00000D   0D                     CARRIAGE RETURN (CR)
       20         20  00000A   0A                     LINE FEED (LF)
      116        116  00000D   0D                     CARRIAGE RETURN (CR)
      117        117  00000A   0A                     LINE FEED (LF)
      166        166  00000D   0D                     CARRIAGE RETURN (CR)
      167        167  00000A   0A                     LINE FEED (LF)
      263        263  00000D   0D                     CARRIAGE RETURN (CR)
      264        264  00000A   0A                     LINE FEED (LF)
      361        361  00000D   0D                     CARRIAGE RETURN (CR)
      362        362  00000A   0A                     LINE FEED (LF)
      388        388  00000D   0D                     CARRIAGE RETURN (CR)
      389        389  00000A   0A                     LINE FEED (LF)

[rcjsuen]

@Mdsp9070 @Frederick888 This should be fixed in the latest 0.4.1 release. Thank you again for the bug report.