prisma1 VS react-app-rewired

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

For more: https://github.com/prisma/prisma1/issues/3830

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

Could you clarify this? Are you referring to the old Prisma 1 Cloud or the new Prisma Data Platform?

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.

Mongoose is quite a standard also open-source, but Prisma is an emerging modern solution that seems to take the cake.

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.

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.

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.

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.

Further information here: https://github.com/timarney/react-app-rewired

Ejecting a React app is a bad idea because our application will lose all the React configurations and will not benefit from the CRA updates. Some solutions for ejecting our application include using packages like react-app-rewired or rewire. You can also use CRACO to eject your React application, but it needs you to install additional plugins.

When created I remove react-script package and copies build dependencies, configuration files and scripts into the app directory. It is needed to modify webpack.config file. (Another solution is to use react-app-rewired

Heads up: CRA5 bumped their webpack dependency to a version that no longer supports node polyfills in browsers. This breaks the builds of nearly all Ethereum-related projects today. A common workaround that avoids ejecting is to hook into the CRA build process. We’re using react-app-rewired but you could simply stay at CRA4 until the community comes up with a better solution.

CRA is good to get something running quick (and it uses webpack underneat!). In the past I've tweaked the webpack config using things like https://github.com/timarney/react-app-rewired when needed, but for all my "serious" projects I ended up ejecting and learning webpack! For my next project I'll try to skip CRA altogether!

// Overrides create-react-app webpack configs without ejecting // https://github.com/timarney/react-app-rewired const { addBabelPlugins, override } = require("customize-cra"); module.exports = override( ...addBabelPlugins( "babel-plugin-myPlugin" /* Add plug-in names here (separate each value by a comma) */ ) );

If Create React App supported Yarn workspaces out-of-the-box, what we've done so far would have been enough to run the app... unfortunately, it doesn't. Luckily, we can use CRACO (or other tools such as customize-cra or react-app-rewired) to customize the Webpack configuration used by Create React App to resolve packages imported from other workspaces.

<--- JS stacktrace ---> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 00007FF69616B9CF v8::internal::CodeObjectRegistry::~CodeObjectRegistry+112159 2: 00007FF6960FCA26 v8::internal::MicrotaskQueue::GetMicrotasksScopeDepth+65430 3: 00007FF6960FD90D node::OnFatalError+301 4: 00007FF696A91BAE v8::Isolate::ReportExternalAllocationLimitReached+94 5: 00007FF696A783AD v8::SharedArrayBuffer::Externalize+78 [1]: https://github.com/timarney/react-app-rewired

Enter react-app-rewired. What this package does is it allows you to hook into the Webpack config process so you can change settings, add loaders or plugins, and so on. It's like having all the pros of ejecting (mainly, access to the webpack.config.js) without actually ejecting.

Switch to craco from react-app-rewired for better CRA v4 support (breaking change!)