Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I can't open Prisma studio when I used npx prisma studio #1027

Closed
parametprame opened this issue Sep 28, 2022 · 1 comment
Closed

I can't open Prisma studio when I used npx prisma studio #1027

parametprame opened this issue Sep 28, 2022 · 1 comment

Comments

@parametprame
Copy link

Bug description

image

How to reproduce

I used npx prisma prisma studio

Expected behavior

Can open prisma studio on browser

Prisma information

risma : 4.3.1
@prisma/client : 4.4.0
Current platform : darwin-arm64
Query Engine (Node-API) : libquery-engine c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Migration Engine : migration-engine-cli c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine : introspection-core c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary : prisma-fmt c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Format Wasm : @prisma/prisma-fmt-wasm 4.3.0-32.c875e43600dfe042452e0b868f7a48b817b9640b
Default Engines Hash : c875e43600dfe042452e0b868f7a48b817b9640b
Studio : 0.473.0

Environment & setup

  • OS: Mac OS
  • Browser: Chrome
  • Database: PostgreSQL

Prisma logs

Invalid string length RangeError: Invalid string length at JSON.stringify (<anonymous>) at xt.serialize (http://localhost:5555/assets/index.js:1:49974) at xt.update (http://localhost:5555/assets/index.js:1:12197) at Cc (http://localhost:5555/assets/vendor.js:50:6994) at xt.n (http://localhost:5555/assets/vendor.js:50:6688) at xt.update (http://localhost:5555/assets/index.js:1:49831) at Cc (http://localhost:5555/assets/vendor.js:50:6994) at xt.n (http://localhost:5555/assets/vendor.js:50:6688) at http://localhost:5555/assets/index.js:1:83936 at Array.forEach (<anonymous>)

@petradonka
Copy link
Contributor

It looks like you're running into an existing issue we're aware of. Could you give this workaround (#895 (comment)) a shot and see if it works for you?

@janpio janpio closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants