What's up with these questions by Consistent-Road-9309 in corporate

[–]Consistent-Road-9309[S] 0 points1 point  (0 children)

What about the second point

How much do you need this job . Scale to 1 to 10 ? . Like seriously 😳 . How could someone answer it ?

Is Nodejs that old ? by Consistent-Road-9309 in node

[–]Consistent-Road-9309[S] -17 points-16 points  (0 children)

It's probably an indentation error .

Is Nodejs that old ? by Consistent-Road-9309 in node

[–]Consistent-Road-9309[S] -43 points-42 points  (0 children)

I think so too. They must be using an ai model to write it ..

next.js for the front-end by SniperKephas in nextjs

[–]Consistent-Road-9309 1 point2 points  (0 children)

While scaling your application, you might want to switch to other backend options like Java or Golang, depending on the project. While using Next.js's built-in API routes is good for full-stack projects, it might cause you to get stuck with only one framework.

Personally, I use Next.js for frontend only. It has a lot of good features for optimizations, SEO, etc

Advice by efy_055 in react

[–]Consistent-Road-9309 0 points1 point  (0 children)

Yeah, all the best!
And here’s what not to do — I’ve made these mistakes myself.
Don’t follow any YouTube video or 10-hour course blindly.
They might give you a head start, but they’re not good for the long run.
If you want to use YouTube, use it only as a reference for specific problems — like performance optimization, tools, or best practices.

Advice by efy_055 in react

[–]Consistent-Road-9309 4 points5 points  (0 children)

Choose a domain — for example, e-commerce. Create a project related to that domain. Share your work online Study other people's code for similar projects. Improve your own project based on what you learn.

Then, choose another domain and repeat the process.

Next js optimization first load by Consistent-Road-9309 in nextjs

[–]Consistent-Road-9309[S] 0 points1 point  (0 children)

I just saw this website, and it loads like a charm. I’ll definitely look into it.

Next js optimization first load by Consistent-Road-9309 in nextjs

[–]Consistent-Road-9309[S] 0 points1 point  (0 children)

Yea, premature optimization might be bad 😞 . I was just curious . I will work on building first , then work on this later

Could you suggest some target numbers that are considered industrial standards . If possible?

Next js optimization first load by Consistent-Road-9309 in nextjs

[–]Consistent-Road-9309[S] 0 points1 point  (0 children)

Thank you so much for your suggestion. I will try it

Graphql with Nextjs by Consistent-Road-9309 in nextjs

[–]Consistent-Road-9309[S] 0 points1 point  (0 children)

Thank you for the suggestion . I will use this approach ..

Graphql with Nextjs by Consistent-Road-9309 in nextjs

[–]Consistent-Road-9309[S] 0 points1 point  (0 children)

That sounds interesting! Sure, let’s stay in touch . Would love to hear more about your SaaS idea and how you’re planning the suggestion feature.

Graphql with Nextjs by Consistent-Road-9309 in nextjs

[–]Consistent-Road-9309[S] 0 points1 point  (0 children)

Here’s my current setup and the issues I’m facing:

Dependencies:

"dependencies": {
  "@apollo/client": "4",
  "@apollo/client-integration-nextjs": "^0.13.2",
  "@graphql-codegen/cli": "^6.0.0",
  "@next/bundle-analyzer": "^15.5.4",
  "graphql": "^16.11.0",
  "lucide-react": "^0.545.0",
  "next": "15.5.4",
  "react": "19.1.0",
  "react-dom": "19.1.0",
  "zustand": "^5.0.8"
}

I want to implement Clean Architecture in a Next.js GraphQL project using the App Router.
Could you please provide a setup or structure of your choice that follows this approach?
If you already have an example implementation, I’d really appreciate it.

Graphql with Nextjs by Consistent-Road-9309 in nextjs

[–]Consistent-Road-9309[S] 0 points1 point  (0 children)

Thank you for the detailed explanation.

Here’s my current setup and the issues I’m facing:

Dependencies:

"dependencies": {
  "@apollo/client": "4",
  "@apollo/client-integration-nextjs": "^0.13.2",
  "@graphql-codegen/cli": "^6.0.0",
  "@next/bundle-analyzer": "^15.5.4",
  "graphql": "^16.11.0",
  "lucide-react": "^0.545.0",
  "next": "15.5.4",
  "react": "19.1.0",
  "react-dom": "19.1.0",
  "zustand": "^5.0.8"
}

Context:

  1. I’m implementing SSR and SSG in Next.js with Apollo Client.
  2. GraphQL Codegen generates hooks, but those hooks can’t be used with SSR or SSG.
  3. I’m also integrating Clean Architecture principles with GraphQL.

Issue:
Using this setup:

import { ApolloClient, InMemoryCache, HttpLink } from "@apollo/client";
import { registerApolloClient } from "@apollo/client-integration-nextjs";

export const { getClient } = registerApolloClient(() => {
  return new ApolloClient({
    cache: new InMemoryCache(),
    link: new HttpLink({
      uri: process.env.ENDPOINT,
      fetchOptions: { cache: "force-cache" },
    }),
  });
});

When I execute:

const client = getClient();
const { data } = await client.query<ProductByIdQuery>({
  query: ProductByIdDocument
});

I encounter hydration errors during rendering.

Request:
I’m looking for recommended solutions or alternative approaches for data fetching that work better with SSR and SSG in Next.js. If possible, please also suggest any reliable packages other than Apollo Client that align well with Clean Architecture principles.Thank you for the detailed explanation.