P
Prisma3mo ago
aamir

Prisma VSCode extension v5.13.1 causing severe issue

Hey team! I have been using Prisma ORM for few months now and it has worked wonders for me, but a few days ago i started facing issue in my schema.prisma file, it stopped formatting and syntax highlighting etc. after a lot of debugging the issue I found was that when i am using VSC extension of Prisma on v5.13.1 it stops working, all the features like formatting etc stops and alongside that when i use Prisma: Restart Language Server it gives error Command 'Prisma: Restart Language Server' resulted in an Error (screenshot attached), but when I downgrade the extension to v5.12.1 it starts working back as usual. Attaching screen recording of VSCode on both the versions of extension on same file. Hope this could get fixed soon! Thanks a ton! Cheers.
No description
5 Replies
jonfanz
jonfanz3mo ago
Thanks for the report, I’ll pass it along to our eng team
druue
druue3mo ago
Hey @aamir can you confirm what OS you're on? Looks like windows to me; I can't reproduce this locally on my mac Although, checking this on my windows PC, I still can't confirm this :thinking: Could you please confirm what version of VS Code you're on?
aamir
aamir3mo ago
I'm using windows 11 with WSL2 (Ubuntu 22.04) Here are Details of VsCode: Version: 1.88.1 (user setup) Commit: e170252f762678dec6ca2cc69aba1570769a5d39 Date: 2024-04-10T17:41:02.734Z Electron: 28.2.8 ElectronBuildId: 27744544 Chromium: 120.0.6099.291 Node.js: 18.18.2 V8: 12.0.267.19-electron.0 OS: Windows_NT x64 10.0.22631
druue
druue3mo ago
I can't reproduce it on the following specs on mac
Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:43:08.196Z (2 wks ago)
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 21.6.0
Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:43:08.196Z (2 wks ago)
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 21.6.0
Nor on the following two windows set ups
- Version: 1.82.2 (user setup)
- Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
- Date: 2023-09-14T05:55:25.390Z
- Electron: 25.8.1
- ElectronBuildId: 23779380
- Chromium: 114.0.5735.289
- Node.js: 18.15.0
- V8: 11.4.183.29-electron.0
+ Version: 1.88.1 (user setup)
+ Commit: e170252f762678dec6ca2cc69aba1570769a5d39
+ Date: 2024-04-10T17:41:02.734Z
+ Electron: 28.2.8
+ ElectronBuildId: 27744544
+ Chromium: 120.0.6099.291
+ Node.js: 18.18.2
+ V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.19045
- Version: 1.82.2 (user setup)
- Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
- Date: 2023-09-14T05:55:25.390Z
- Electron: 25.8.1
- ElectronBuildId: 23779380
- Chromium: 114.0.5735.289
- Node.js: 18.15.0
- V8: 11.4.183.29-electron.0
+ Version: 1.88.1 (user setup)
+ Commit: e170252f762678dec6ca2cc69aba1570769a5d39
+ Date: 2024-04-10T17:41:02.734Z
+ Electron: 28.2.8
+ ElectronBuildId: 27744544
+ Chromium: 120.0.6099.291
+ Node.js: 18.18.2
+ V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.19045
I don't have anything on windows 11 to test it on but if you have any other systems that you could cross-verify with, that'd be a big help!
aamir
aamir3mo ago
Sure I did test this on a fresh computer with windows 11 and fresh install of VSCode and it seems to work fine for that. I'll try and reset my VSCode settings and everything and will try using prisma's newer extension. I'll update here if the results are any different. Thanks a ton for your help though! 🫂