Failed to download Prisma engines for darwin-arm64
See original GitHub issueBug description
Downloading Prisma engines for Node-API for darwin-arm64 [==== ] 65%
it got stuck when I run npx prisma -v
How to reproduce
Run npx prisma -v
Expected behavior
No response
Prisma information
// Add your schema.prisma
// Add your code using Prisma Client
Environment & setup
- OS: macOS
- Database: SQLite
- Node.js version: 18.11.0
Prisma Version
4.6.1
Issue Analytics
- State:
- Created 10 months ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Prisma engines
By default, all engine files are automatically downloaded into the node_modules/@prisma/engines folder when you install or update prisma , the Prisma CLI ...
Read more >Prisma query engine not found on mac M1 - Stack Overflow
I've noticed that the libquery_engine-darwin.dylib.node file actually exists as libquery_engine-darwin-arm64.dylib.node . My schema.prisma ...
Read more >SvelteKit & Prisma - A match made in digital heaven
Prisma is a pretty genius way to achieve that. With SvelteKit, you get client & server-side data fetching - the best of both...
Read more >@prisma/engines-version - npm
This package exports the Prisma Engines version to be downloaded from Prisma CDN.. Latest version: 4.9.0-2.c8f7657d570c599bdb5ffd72b92e5123c3b07175, ...
Read more >js query engine for university courses - kandi
Implement Query-Engine with how-to, Q&A, fixes, code snippets. kandi ... You can download it from GitHub. ... Prisma query engine not found on...
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 FreeTop 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
Top GitHub Comments
This is all definitely a problem with your local connectivity, the URLs work fine globally. Check if your network is somehow blocking AWS, Cloudfront or similar.
@jsdude0220 just tried to downgrade my node to 16.18.1 and the download works now. Not sure it is the cause of a deprecated api from nodejs