Module imports not working on Windows about janet-lsp HOT 4 CLOSED

Not Windows, but seemingly similar issue for a non-root install of janet on a linux box:

from janet-lsp.

@sogaiu I just published a pre-release version of Janet++ that bundles Janet LSP as a .jimage rather than a compiled executable. This means that when the Language Server starts up, it will be running on the user's locally-installed copy of Janet (assuming janet is on the user's path, which it ought to be). In my preliminary testing, this seems to fix the module import issue, since the Language Server is running as the user's own install which means it should discover modules the same way any other invocation of janet on their system would.

Would you like to test this on your non-root Void Linux install? You can do so by switching to the Pre-release version on the extension page in VS Code:

from janet-lsp.

@CFiggers Thanks for the heads up.

I gave it a try and it seems to be working better 👍

from janet-lsp.

Fixed in Janet++ by running the LSP from a .jimage rather than a compiled executable. May need to revisit in the future if Janet LSP will be a stand-alone CLI tool in addition to editor integration.

from janet-lsp.