We should move away from @vercel/ncc at some point, and stop relying on whatever magic they're doing behind the scenes to bundle up code.

It's a dice roll whether a new ncc release will work. It would be better if we had more control over the build step (with something like webpack maybe).

First use case will likely be receiving friend requests.

Lighter weight than Apollo.

For both preview and production deployments, the live URL from AWS (or whatever provider) should be posted back in the PR comments.

This way devs won't have to switch to the AWS Console to see their changes.

• The GraphQL playground is currently accessible in production, but should be disabled
• Can be accomplished by setting Lambda env variable NODE_ENV to "production"

• Ensure that emojis set on a user's status are valid

Right now two separate serverless workflows are maintained: one for preview deploys and one for production deploys.

As these get more complicated and logic gets duplicated between them, it'd be nice to have the workflows consolidated in one spot.

Error message:

server_1  | Nexus Schema Typegen: Expected module /app/.build/api/server/context.js to be an absolute path to a TypeScript module, skipping.
server_1  | 🚀 Server ready at http://localhost:3000
server_1  | Missing required typegen import: ContextModule

It's blocked because of the relation between User and FriendRequest (and maybe Friendship).

Or, continue to use it, and migrate to the new version once available.

• DB seeding preview
• Migrations improvements
• Does the $.count update impact anything?