RickNMortyCompose VS Next.js

// /src/relay/environment.ts import { Store, RecordSource, Environment, Network, Observable, } from "relay-runtime"; import type { FetchFunction, IEnvironment } from "relay-runtime"; const fetchFn: FetchFunction = (params, variables) => { const response = fetch("https://rickandmortyapi.com/graphql/", { method: "POST", headers: [["Content-Type", "application/json"]], body: JSON.stringify({ query: params.text, variables, }), }); return Observable.from(response.then((data) => data.json())); }; export function createEnvironment(): IEnvironment { const network = Network.create(fetchFn); const store = new Store(new RecordSource()); return new Environment({ store, network }); }

import type { CodegenConfig } from '@graphql-codegen/cli'; const config: CodegenConfig = { overwrite: true, schema: "https://rickandmortyapi.com/graphql", documents: './**/*.graphql', generates: { "src/graphql/generated/graphql.ts": { plugins: ['typescript', 'typescript-operations', 'typescript-react-apollo'], }, config: { withHooks: true } } }; export default config;

export const apolloClient = new ApolloClient({ uri: "https://rickandmortyapi.com/graphql", cache: new InMemoryCache({ typePolicies: { Query: { fields: { characters: { keyArgs: false, merge(existing: Characters, incoming: Characters) { return { ...incoming, results: [ ...(existing?.results || []), ...(incoming?.results || []), ], } satisfies Characters; }, }, }, }, }, }), });

goctopus -a rickandmortyapi.com _ __ _ ___ ___| |_ ___ _ __ _ _ ___ / _` |/ _ \ / __| __/ _ \| '_ \| | | / __| | (_| | (_) | (__| || (_) | |_) | |_| \__ \ \__, |\___/ \___|\__\___/| .__/ \__,_|___/ v0.0.14 |___/ |_| [INF] Enumerating subdomains for 'rickandmortyapi.com' [INF] Found 5 subdomains for 'rickandmortyapi.com' in 15 seconds 276 milliseconds INFO[0016] Done fingerprinting rickandmortyapi.com INFO[0016] Found: {"authenticated":false,"domain":"rickandmortyapi.com","schema_status":"OPEN","source":"rickandmortyapi.com","url":"https://rickandmortyapi.com/graphql"} INFO[0016] Done. Found 1 graphql endpoints

Checkout https://rickandmortyapi.com and their https://rickandmortyapi.com/graphql

import { ApolloClient, InMemoryCache, ApolloProvider } from "@apollo/client"; Import PeopleData from './PeopleData' function App() { const client = new ApolloClient({ cache: new InMemoryCache(), uri: "https://rickandmortyapi.com/graphql", }); return (

); } export default App;

Back to business: fortunately, Postman has built-in full support for GraphQL! 🎉Let's take a quick tour of the capabilities by exploring the Rick and Morty API. To get started, create a new HTTP request in Postman. Set the request mode to POST and the URL to https://rickandmortyapi.com/graphql. Now; in the body section, select GraphQL. You should end up with something like this:

import "@/styles/globals.css"; import type { AppProps } from "next/app"; import { ApolloClient, InMemoryCache, ApolloProvider } from "@apollo/client"; const client = new ApolloClient({ uri: "https://rickandmortyapi.com/graphql", cache: new InMemoryCache(), }); export default function App({ Component, pageProps }: AppProps) { return ( ApolloProvider> ); }

import React from 'react'; import ReactDOM from 'react-dom/client'; import './index.css'; import App from './App'; import { ApolloClient, ApolloProvider, InMemoryCache } from '@apollo/client' const client = new ApolloClient({ uri: "https://rickandmortyapi.com/graphql", cache: new InMemoryCache(), }) const root = ReactDOM.createRoot(document.getElementById('root')); root.render( );

I have a next.js app that uses dynamic routes. Here is the repo on Github https://github.com/ChristianOConnor/graphql-next-api-tester. Run the app by cloning the repo and cd-ing into the root directory, running npm install then npm run dev. It works perfectly. It's a next.js app that does graphql calls to https://rickandmortyapi.com/graphql, and renders them out into a table. You first click on the "List of characters" button in the middle of the home page: [![enter image description here][1]][1]

https://github.com/vercel/next.js/discussions/27666 One of them said 'renaming folder to uppercase' might cause trouble. git might not recognize case-sensetive changes by default.

Next.js has long cemented itself as one of the front runners in the web framework world for JavaScript/TypeScript projects so we’re going to be using that. More specifically we’re going to be using V14 of Next.js which allows us to use some exciting new features like Server Actions and the App Router.

Web frameworks like Next.js will usually include this feature, but do check that they set the caching headers correctly!

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.

Would you like to elaborate on that?

In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.

For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/

Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/

Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main

Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/

React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.

Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.

Next.js: For the website and the admin dashboard

Until the time of writing, there is no official example of how to enable runtime environmental variables in a Dockerized Next.js app, as utilizing unstable_noStore would only dynamically evaluate variables on the server (node.js runtime). There is also an interesting discussion regarding this topic on GitHub.

next.js is a very popular React framework. remix-adonisjs includes more functionality through the AdonisJS backend ecosystem, and should be easier to self-host and self-manage.

Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.

For more information, check out this issue.