Next

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
Platform: darwin
Arch: x64
Version: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64
Binaries:
Node: 16.15.0
npm: 8.5.5
Yarn: 3.2.0
pnpm: 6

Anytime I open up the options for a plugin the okey button (I think that's what it's called but I can't see it) is half cut off

macOS version: Monterey (12.3.1)
Kap version: 3.5.4

What do you want and why?

I want an exported getQueryData function that takes in a resolver.

Instead of having to get the query key manually, such as below

const queryKey = getQueryKey(getTasks, { taskListId })
const tasks = queryClient.getQueryData<PromiseReturnType<typeof getTasks>>(queryKey)

I want to be able to write

const tasks = getQueryData(getTasks, { 

Question 💬

In the type definition for JWTEncodeParams, maxAge is defined as optional.

export interface JWTEncodeParams {
    /** The JWT payload. */
    token?: JWT;
    /** The secret used to encode the NextAuth.js issued JWT. */
    secret: string | Buffer;
    /**

Without all the marketing.

Would be supercool to have "BlogPosting" as article JSON-LD type.

From the Google Docs (https://developers.google.com/search/docs/data-types/article#non-amp):

Article objects must be based on one of the following schema.org types: Article, NewsArticle, BlogPosting. (https://schema.org/BlogPosting)

I tried to use "BlogJsonLd" as type for Blogposts, but the Google Rich Result Test (https:

Issue Summary

Building with serverless results in an error:

Build error occurred
TypeError: Class extends value undefined is not a

Currently with the new typesafe env-vars, they are all placed under server. We should probably have some distinction for client-side env-vars as Theo pointed out on stream when using Pusher for example.

Things like Optional Chaining should be transpiled for e.g. node 12 compatibility: https://esbuild.github.io/content-types/#javascript. We should choose es2016 for all packages.