prisma1
babel-plugin-transform-typescript-metadata
prisma1 | babel-plugin-transform-typescript-metadata | |
---|---|---|
64 | 1 | |
16,816 | 215 | |
- | - | |
5.1 | 0.0 | |
over 1 year ago | 8 months ago | |
Scala | JavaScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
prisma1
-
🏆 Top Scala open source projects and contributors
I was surprised to see Prisma (a js library) listed, digging more I found out that they indeed had an Scala project which is now archived https://github.com/prisma/prisma1
-
Hyperstack - a new open source Node.js web framework with everything included
For more: https://github.com/prisma/prisma1/issues/3830
-
Show HN: WunderBase – Serverless OSS Database on Top of SQLite, Firecracker
Hey there, I'm Nikolas from the Prisma team. Just came here to quickly clarify this notion:
> Prisma is an API server that puts a GraphQL API in front of a DB.
Prisma is an ORM which generates a JavaScript/TypeScript client library for your database.
Your description is very true for Prisma 1 (which has been in maintenance mode for several years and is officially deprecated by now [1]), but the latest version(s) of Prisma (v2+) don't expose a GraphQL API any more. Prisma 1 also used GraphQL SDL for data modeling, the Prisma ORM on the other hand has its own, custom modeling language for describing database schemas in a declarative way and also comes with a flexible migration system.
That being said (and as Jens also mentioned elsewhere), the Prisma ORM does use GraphQL _internally_ as a wire protocol. However, as a developer, you _never_ touch this internal GraphQL layer and are not even supposed to be aware of it (you actually have to jump through a lot of hoops to even "find" it). It's also very likely that we'll replace GraphQL as a wire protocol in the future, so "GraphQL" really isn't something you should be thinking about as a developer who is using Prisma.
Hope that clarifies the situation a bit, let me know if you have any further questions around this topic.
[1] https://github.com/prisma/prisma1/issues/5208
-
Why is Prisma so popular and who the hell is using it for production?
Could you clarify this? Are you referring to the old Prisma 1 Cloud or the new Prisma Data Platform?
-
Comparing 4 popular NestJS ORMs
First released in 2019, Prisma is the newest ORM of the four we discussed. It will need time to get to a more mature state. Recently, the release of version 3 introduced a few breaking changes. There are also some existing issues noted in GitHub, such as that it does not support some Postgres column types.
-
Preferred SQL ORM
Mongoose is quite a standard also open-source, but Prisma is an emerging modern solution that seems to take the cake.
-
What is Blitz.js & How to Get Started With It
Well, here comes Blitz, the agnostic monolith. Take the database, for example - Blitz comes out-of-the-box with Prisma 2. However, you're free to switch to another one like Fauna or DynamoDB. The same goes for the configuration; deciding a folder structure, defining routing conventions, selecting a styling library, and adding authorization and authentication are all set up by default, but that doesn't mean you cannot go your own way.
-
Rakkas: Next.js alternative powered by Vite
There is also a RealWorld port (Rakkas implementation of the RealWorld specification), a simple but complete fullstack application demonstrating how to approach building a REST API, accessing your database (via Prisma), handling authentication, testing, and more.
-
GraphQL & REST with Prisma and Azure SQL: love at first sight!
If you're into Typescript and prefer a code-first approach when working with databases, you'll be happy to learn about Prisma! Prisma is a next-generation Node.js and TypeScript ORM, that allows you to define a schema using a dedicated DSL so that you can then have all the comforts of modern development environments like intellisense, static type checking, automatic scaffolding and more.
-
Is NextJS a server side framework?
It is a frontend framework, but with API routes and ORMs like https://www.prisma.io/ , you could use it as a complete stack in traditional sense I suppose.
babel-plugin-transform-typescript-metadata
-
Feedback on experiences with TypeORM vs the other contenders
MikroORM is a little better in that they have an alternative strategy that only requires your build tool to support type (1) but not type (2) https://github.com/leonardfactory/babel-plugin-transform-typescript-metadata
What are some alternatives?
sveltekit-prisma - A sample repository to show how SvelteKit and Prisma work together.
decky - Zero-bundle-size decorators for TypeScript
inertia-laravel - The Laravel adapter for Inertia.js.
jsx-control-statements - Neater If and For for React JSX
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
htm - Hyperscript Tagged Markup: JSX alternative using standard tagged templates, with compiler support.
graphql-helix - A highly evolved GraphQL HTTP Server 🧬
Objection.js - An SQL-friendly ORM for Node.js
nestjs-typegoose - Typegoose with NestJS
apollo-server - 🌍 Spec-compliant and production ready JavaScript GraphQL server that lets you develop in a schema-first way. Built for Express, Connect, Hapi, Koa, and more.
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
prisma-client-go - Prisma Client Go is an auto-generated and fully type-safe database client