Feel free to contact me at robert.balicki@gmail.com or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
Feel free to contact me at robert.balicki@gmail.com or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
| const express = require("express"); | |
| const router = express.Router(); | |
| const User = require("../models/user"); | |
| const AWS = require("aws-sdk"); | |
| AWS.config.update({ | |
| accessKeyId: process.env.accessKeyId, | |
| secretAccessKey: process.env.secretAccessKey, | |
| region: "us-east-1" | |
| }); |
Memoization is a somewhat fraught topic in the React world, meaning that it's easy to go wrong with it, for example, by [making memo() do nothing][memo-pitfall] by passing in children to a component. The general advice is to avoid memoization until the profiler tells you to optimize, but not all use cases are general, and even in the general use case you can find tricky nuances.
Discussing this topic requires some groundwork about the technical terms, and I'm placing these in once place so that it's easy to skim and skip over:
| import { ObjectType, Field } from "@nestjs/graphql"; | |
| @ObjectType() | |
| export class PageInfo { | |
| @Field({ nullable: true }) | |
| startCursor: string; | |
| @Field({ nullable: true }) | |
| endCursor: string; |