apollo-client | Apollo React Hooks with automatic cache updates | GraphQL library

I'm writing a toy app to learn more about Serverless Framework and AWS AppSync etc. I'm trying to do TDD as much as possible. I'm using mock-apollo-client to mock the ApolloClient, and I've run into a problem. When trying to write a test to make sure the arguments to the query are passed, the test always returns a 401 Unauthorized error. It seems as though the real end point is still being called, because when a valid x-api-key is added to the instantiation of the ApolloClient, the test returns the real value from the AppSync server, and not the mock value I'm expecting. I'm using a mock, not spy, so I'm not expecting the real end point to actually be hit. Furthermore When I do add a valid x-api-key the test fails because the function is never called.

I'm attempting to create an apollo client plugin for a Nuxt 3 application. It's currently throwing an error regarding a package called ts-invariant:

Contrast in "apollo-client in next.js" approaches chosen in next-with-apollo npm library and the approach shown in next.js docs.

The link of approach chosen by next.js for apollo client: https://github.com/vercel/next.js/blob/canary/examples/with-apollo/lib/apolloClient.js

In next.js doc approach:

• no third-party library next-with-apollo is used
• no get-data-from-tree is used
• Moreover i found this approach more meaningful and elegant inner-working of client side redering and SSR of apollo-client in next.js. I strongly like this

Some cons in next-with-apollo approach

• in next-with-apollo docs, it is stated that in withApollo API, the parameter getDataFromTree of intialState defaults to undefined by implementaion and its stated "It's recommended to never set this prop, otherwise the page will be a lambda without Automatic Static Optimization "
• get-initial-props is used which is not recommended by next.js for optimization reasons general thing. Why to consider third party library if there is non-third party way and suggested officially unless it has drawbacks?

It made me really curious to see many are using next-with-apollo and rarely seen the usage of the approach shown in next.js docs? I'm curious whether approach in next.js docs has any drawbacks (which i strong think of not having any)?

• does the approach shown in next.js has some drawbacks?
• does next-with-apollo has more efficiencies? if so what r those more efficiencies for which it is wise not to choose next.js doc approach. I wanna be sure that if i'm rejecting next.js doc approach (currently im choosing it) i'm not doing any wrong

So which is better for both client-side data fetching and server-data fetching to support both CSR and SRR?

When I see sample apps which uses Apollo-client I see following constructor.When I read HttpLink document, it seems that graphql endpoint must be set as uribut in following code, I couldn't find them.

My React app is using Webpack + Babel. When I compile in development everything works perfectly well.

When I bundle for production ("npm run build") and upload the bundle in prod, an error appear in the console:

Why? I found a similar question but didn't find an answer : related stackoverflow question

Here's my webpack.prod.js config:

I have a React project using Babel and Webpack. Recently I realized that my webpack wasn't "hot loading" anymore when I make a change in my project files. (this cause me some trouble, anyhow)

I audited my npm dependencies and had 60 vulnerabilities with 9 high and 2 critical. I thought this should be taken care of.

Now, I tried to install the package that seems to broke things (using npm audit) but to no avail. I still got 31 vulnerabilities even after trying to install a different version of React Script.

Now, if I try to start my app, webpack doesn't compile saying "Cannot find module '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining'"

I tried to install the Babel dependencies but every time a new one comes up. I know Babel just recently updated to 7.16 (October 31, 2021). Is this why my problems started?

How should I go about resolving all those dependencies issues? I feel it's a never ending instance of install a new packages that just break another one...

Package.json

I'm trying to implement a global error handling for a React application, which uses Apollo Client 3.4.8.

I'm setting up the App and Apollo like this:

I'm trying to get started with both GraphQL and Svelte using Apollo Server, but all I get is this error "ctx[random number].data is undefined". I also tried svelte {#async} but got the same error. What I'm doing wrong and how to make it works?

I'm facing next problem: I have a useQuery hook for getting usersData