Connection to server got closed. Server will restart.
See original GitHub issueEnvironment: Windows 10 Pro Build 19645.mn_release.200605-1502 with and without WSL 1 Plugin Version: Prisma 2.1.1 VSCode Version: 1.46.1
Error occurs while visiting schema.prisma file.
Error log:
internal/modules/cjs/loader.js:626
throw err;
^
Error: Cannot find module '/home/valentin/.vscode-server/packages/language-server/bin/server.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:623:15)
at Function.Module._load (internal/modules/cjs/loader.js:527:27)
at Function.Module.runMain (internal/modules/cjs/loader.js:837:10)
at internal/main/run_main_module.js:17:11 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
[Info - 6:51:22 PM] Connection to server got closed. Server will restart.
It seems like the extension is searching in the wrong folder for the language-server. I also tried the latest Prisma Insider vscode plugin without any success
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Need help with an error: "Connection to server got closed ...
Type: LanguageService With Visual Studio Code I'm having the issue: Connection to server got closed. Server will not be restarted.
Read more >"Connection to server got closed. Server will not be restarted ...
I am using VSCode on Ubuntu 20.04. The errors, "Connection to server got closed. Server will not be restarted." and "The language server...
Read more >The DAML language server crashed 5 times in last 3 minutes ...
I am following the 'Introduction to DAML' course and getting this error message when opening Main.daml from VS code. I have tried installing/uninstalling ......
Read more >VSCode language server won't start - VS Code - Julia Discourse
task.jl:411 [Info - 12:28:14 AM] Connection to server got closed. Server will restart. ┌ Error: Some Julia code in the VS Code extension ......
Read more >Language Server Extension Guide - Visual Studio Code
This guide will teach you how to build a Language Client / Server using our ... have change in VS Code connection.console.log('We received...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

We released 2.1.4 that fixed this issue.
What happened: We recently restructured this repo to separate the VSCode extension and the language server. The extension was not using the language server npm dependency but instead searched in the corresponding folder in the repo.
We now are only accessing the language server through the npm dependency.
To ensure that this doesn’t happen again, we created the following issue:
Please try out 2.1.4 and let us know if there are any issue with it.
Yeah, I am using macOS, and I see the same thing happening here with 2.1.1 of the Prisma plugin.
I would also note that in the informational page, about the plugin, where it has a link regarding ‘Contributing’, that the link is dead. It would sure be nice if that was fixed too.
ie:
Read more about how to contribute to the Prisma VSCode extension