Next

Run next info (available from version 12.0.8 and up)

No response

What version of Next.js are you using?

canary

What version of Node.js are you using?

16.13.0

What browser are you using?

no

What operating system are you using?

Ubuntu 20.04.3 LTS

How are you deploying your application?

no

Describe the Bug

In response to comment:

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

In vercel/next.js#34316 (comment) I concluded that getInitialProps really does not play well with our auth model. There are simply much better solutions for this now.

We should discourage the usage of it entirely.

https://next-auth.js.org/tutorials/securing-pages-and-api-routes should be updated to also mention [Middleware support](https://next-auth.

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.

Right now the wishlist page shows "Your wishlist is empty" before showing your wishlist items, that should be a loading state instead.

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:

Characters like č ć ž š đ use a fallback font instead of the original one. I believe this issue was not present in the v1. Fonts such as Lato or Montserrat definitely support accented characters, so I think this is a bug.

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.