apollo-client VS notistack

Actually, it's worse than that. Next has started throwing errors if it statically detects you even _importing_ hooks inside of a React Server Component environment:

- https://github.com/apollographql/apollo-client/issues/10974

- https://github.com/apollographql/apollo-client/issues/11167

To the point that Lenz Weber( a maintainer of Apollo Client, and my co-maintainer on Redux Toolkit), is considering resorting to a package that wraps and re-exports all of React's public API just to avoid that static analysis:

- https://github.com/apollographql/apollo-client/pull/11175

Apollo Client (18k ⭐) -> A comprehensive state management library for JavaScript that enables you to manage both local and remote data with GraphQL. Use it to fetch, cache, and modify application data, all while automatically updating your UI.

This currently doesn't work as expected so I have logged this issue in apollo client repo.

I understand this has something to do with the fact, that SvelteKit expects the client and server code to be completely identical - this has already prompted changes to rxjs and apollo is still pending to be fixed. I understand the reason behind being able to run rxjs and apollo on the server but

There is a long-standing issue with error caching (its absence, that is), which leads to errors being rendered as a loading state on the server side. Therefore, if you're doing SSR, you might want to design your schema in such a way that there are no intentional errors in queries whatsoever. To do so, we can use null values instead of NOT_FOUND errors (see how we essentially treated errors as data here?). Note how nothing stops us from setting the response code to 404 in case of a null value, should we want so.

Lol apollo client too.. saw this issue opened like, immediately after the release https://github.com/apollographql/apollo-client/issues/10231

There were some caching issues, outlined here https://github.com/apollographql/apollo-client/issues/6916 to be aware of

If you look at how major backend projects structure their code, it's almost always object-oriented TypeScript.

I submit for the record:

- Apollo Client: https://github.com/apollographql/apollo-client/blob/main/src...

- Storybook: https://github.com/storybookjs/storybook/blob/next/lib/chann...

- Nest: https://github.com/nestjs/nest/blob/master/packages/core/nes...

- MongoDB Driver: https://github.com/mongodb/node-mongodb-native/blob/main/src...

- Prisma: https://github.com/prisma/prisma/blob/main/packages/engine-c...

[※Alert: The following is a code example using the Apollo Client notation, but the Apollo Client does not support Suspense at this time. Github issue about Suspense support: https://github.com/apollographql/apollo-client/issues/9627]

GitHub link: GitHub – iamhosseindhv/notistack

command dependency function npm i cudosjs https://www.npmjs.com/package/cudosjs A JavasSript Open Source Library for https://cudos.org/  network npm i react-router-dom https://www.npmjs.com/package/react-router-dom It contains bindings for the routing library for React npm i react-hook-form https://www.npmjs.com/package/react-hook-form Performant, flexible and extensible forms with easy to use validation. npm i zod https://www.npmjs.com/package/zod A type declaration and validation library. We use it to declare and validate the data type of the forms used in NFT minting. npm i @hookform/resolvers https://github.com/react-hook-form/resolvers allows you to use an external validation library with React hook form npm i @mui/material @mui/lab @emotion/react @emotion/styled https://mui.com/material-ui/getting-started/overview/ for component styling Material UI is an open-source React component library that implements Google's https://m2.material.io/ . npm i notistack https://www.npmjs.com/package/notistack For snack bar notification npm i @fontsource/poppins Poppins font Poppins font via Fontsource npm i @keplr-wallet/types npm install @esbuild-plugins/node-globals-polyfill To make the Node module Buffer available in our project

Use library like Notistack https://notistack.com/

The notification system is highly application-dependent. We can create something custom or use a library like notistack. For the sake of simplicity, we’ll assume the use of notistack from now on, but the actual implementation doesn’t really matter.

notistack is used (which is actually based on MUI Snackbar) + some custom integration with the store.

For the front-end, there are several open-source React libraries to choose from. At Courier, we recommend react-toastify. Alternatively, you could use a framework like react-hot-toast or notistack.