Next

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Binaries:
  Node: 16.14.0
  npm: 8.3.1
  Yarn: 1.22.17
  pnpm: 6.32.

What do you want and why?

If a user has a react-final-form with a JS Set (or Map) in the initial values, the form resets on some activities, e.g. switching to another tab.

Possible implementation(s)

This can be fixed by using the initialValuesEqual prop:

import deepEqual from "fast-deep-equal"

    <FinalForm
      initialValues={initialValues}
      initialValues

Description 📓

https://github.com/nextauthjs/next-auth/blob/7636de4a340380c50dea39be3854d9b7d69be62b/packages/next-auth/src/next/middleware.ts#L84

Middleware is calling getToken directly without providing any decode methods. By getToken() uses jwtDecrypt from jose package, and it will probably throws error when the JWT is not signed in the same way. It will throw error when we p

Description

I'm using a number field with the GQL + Tina Cloud setup and realized that there is a bug in the number field. If you edit the field, e.g. from empty to 100 and then remove the 100 again, an error occurs when saving the value. If I do not touch the fields at all tho it does accept it when they are empty. Here's a video to illustrate:

https://user-images.githubusercontent

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

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.