You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logs from Developer Tools Console or Command line, if any:
<img width="448" alt="image" src="https://user-images.githubusercontent.com/68872269/167610455-c36929c0-eb20-434c-a95a-cb73c9320721.png">
Invalid string length
RangeError: Invalid string length
at JSON.stringify (<anonymous>)
at _t.serialize (http://localhost:5555/assets/index.js:1:49091)
at _t.update (http://localhost:5555/assets/index.js:1:12197)
at Cc (http://localhost:5555/assets/vendor.js:50:6994)
at _t.n (http://localhost:5555/assets/vendor.js:50:6688)
at _t.update (http://localhost:5555/assets/index.js:1:48948)
at Cc (http://localhost:5555/assets/vendor.js:50:6994)
at _t.n (http://localhost:5555/assets/vendor.js:50:6688)
at http://localhost:5555/assets/index.js:1:82151
at Array.forEach (<anonymous>)
Does the issue persist even after updating to the latest prisma CLI dev version? (npm i -D prisma@dev)
yes
Prisma schema (if relevant):
The text was updated successfully, but these errors were encountered:
prisma -v
ornpx prisma -v
):prisma : 3.14.0-dev.60
@prisma/client : 3.10.0
Current platform : darwin-arm64
Query Engine (Node-API) : libquery-engine 2b0c12756921c891fec4f68d9444e18c7d5d4a6a (at node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Migration Engine : migration-engine-cli 2b0c12756921c891fec4f68d9444e18c7d5d4a6a (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine : introspection-core 2b0c12756921c891fec4f68d9444e18c7d5d4a6a (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary : prisma-fmt 2b0c12756921c891fec4f68d9444e18c7d5d4a6a (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Default Engines Hash : 2b0c12756921c891fec4f68d9444e18c7d5d4a6a
Studio : 0.460.0
prisma
CLI dev version? (npm i -D prisma@dev
)yes
The text was updated successfully, but these errors were encountered: