End of Support for Studio Electron app

[martzoukos]

Hello,

we are planning to stop support for the Electron version of the Studio app in 4 weeks.
This means that after March 1st we will stop releasing new versions of the Electron app that will be compatible with the latest Prisma ORM versions.

You will still be able to use:

• The CLI version of Studio (by running npx prisma studio)
• The Data Browser in the Prisma Data Platform for your online database instances

The reasons for this move have to do with the low adoption of Electron Studio (as opposed to the CLI version) compared with the maintenance needs.

Let us know if you hove any questions in this issue.

Thank you.

[saikojosh]

For anyone else this impacts, if you're using Chrome you can get similar functionality by saving the Prisma Studio URL used by the CLI (http://localhost:5555) as a PWA;

npx prisma studio, open in Chrome, and then go to Chrome menu -> More tools -> Create shortcut... and tick the "open in window" option.

[potts99]

Would this be open to the community to take over maintenance or no?

[ezeikel]

Could you also remove the Studio from products on the website? Just downloaded the app today to then found this Issue 😅

[Jolg42]

@ezeikel So Studio as a product is not going away, only the Electron App.

Maybe you are talking about this page here https://www.prisma.io/studio which will get updated later to remove the download links to the Electron app and switch to the CLI usage.

[ezeikel]

@Jolg42 Ok great. Yeah, I just meant the download links for the Electron App. Just tried the CLI version and it works great 👌🏿

[fairking]

In my opinion the desktop app (electron) is better so you don't have to run cli. You just click the shortcut and you have your app. When you close the app, it goes offline. It is much simpler. I know electron is a little bit harsh regarding its setup and use in development (I went through bushes with thorns too). But I feel the desktop app could be better to use in everyday life.

P.S. Think of phpmyadmin vs mssql manager.

[ZhaoKunLong]

@martzoukos I just upgraded to prism studio. And then I see this prompt if It's doesn't support anymore, can I continue to use the old version, because I have the previous version's installer saved locally. I pretty much like this app on Mac, Coz I don't want to use pgAdmin. 😄

[VinylVault]

honestly, although Studio app may be a small % of uptake, i think it is extremely short sighted to be discontinued.

personally, I hate the CLI version, with the App, I can look at the data in the tables so much more efficiently. (its not another Browser tab I have to keep open too)

please re-consider this, or at least let the community keep this brilliant tool upto date and active.

[huv1k]

I am just sad that Prisma is going full-on abandonware.

[Powersource]

My biggest annoyance with this is that I don't like to install things using npx. Is it available as a tar.gz or simple binary somewhere? Then people could easily package it for distros.

[hansnijssen]

There's allways DBGate, an Electron DB manager. I use it all the time and it's really slick !
https://dbgate.org/
it even has a designer mode, and it's open source (mit)

[ekkis]

There's allways DBGate, an Electron DB manager. I use it all the time and it's really slick ! https://dbgate.org/ it even has a designer mode, and it's open source (mit)

seems like a nice tool but when creating a connection it doesn't allow pasting in values. so I had to struggle with an enormously long password where I can't tell a lowercase "L" from an uppercase "i" or a zero from an uppercase "o". how infuriatingly stupid. but it works and it seems full fledged

[hansnijssen]

Hi ekkis, that's weird, must be something odd at your side, since I always copy-paste without problems....I always use the keyboard: (ctrl-c ctrl-v) but my guess is you allready tried that?

[ekkis]

yes, of course. maybe it's an issue on OS/X

[Suya1671]

https://www.prisma.io/studio checked today, shows NPX. A cool idea imo would be to use something like tauri or maybe make it a PWA instead of a CLI utility.

[furudean]

My biggest annoyance with this is that I don't like to install things using npx. Is it available as a tar.gz or simple binary somewhere? Then people could easily package it for distros.

npm i -g prisma
prisma studio

[Powersource]

My biggest annoyance with this is that I don't like to install things using npx. Is it available as a tar.gz or simple binary somewhere? Then people could easily package it for distros.

npm i -g prisma
prisma studio

The reason I don't like using npx is because it installs stuff globally using npm. Npm is good for managing deps in a package but I don't want it touching my system, I already have other much better tools for that (my OS package manager).

[jbolthouse]

I'd recommend dev containers and containerized workloads. Makes it easier to run tooling like npx in a more targeted way. I realize that might not be feasible in situations where you have no control of your infra. But if you do, definitely consider docker or podman in your dev toolchain. I wil sometimes have 2 or 3 prima studios running at a time all from different container workloads.

…

On Tue, Apr 25, 2023, 5:27 AM Jacob Karlsson ***@***.***> wrote: My biggest annoyance with this is that I don't like to install things using npx. Is it available as a tar.gz or simple binary somewhere? Then people could easily package it for distros. npm i -g prisma prisma studio The reason I don't like using npx is because it installs stuff globally using npm. Npm is good for managing deps in a package but I don't want it touching my system, I already have other much better tools for that (my OS package manager). — Reply to this email directly, view it on GitHub <#845 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACKXZBSDOVOWE53JKRTKGTXC67LRANCNFSM5NGGBIBA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[furudean]

The reason I don't like using npx is because it installs stuff globally using npm. Npm is good for managing deps in a package but I don't want it touching my system, I already have other much better tools for that (my OS package manager).

An alternative is putting prisma in the scripts section of your package.json and calling it like so:

npm run prisma -- migrate dev

This will reference the prisma cli installed in your package definition

[Powersource]

I'd recommend dev containers and containerized workloads. Makes it easier
to run tooling like npx in a more targeted way.

Cool that that works for you but for me, using docker to run this feels like massive overkill. I'm just asking for a tarball here, nothing fancy.