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 19.6.0: Sun Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64
Binaries:
  Node: 16.5.0
  npm: 8.3.0
  Yarn: 1.17.3
  pnpm: N

https://github.com/vercel/swr/blob/43f01571f0a985b5b62792059efe18835c508a94/examples/autocomplete-suggestions/pages/index.js#L21

I know this is only sample code, ... but I can see this suddenly ending up in lost of places verbatim, especially now that we have AI's writing most of our code :D (grin)

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

blitz b -> blitz build
blitz p -> blitz prisma
blitz c -> blitz console

etc

Provider type

Custom provider

Environment

next-auth 4.3.3
(I don't think any other version information is relevant, I looked at the source)

Reproduction URL

N/A

Describe the issue

I looked at the source and the declaration seems t

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:

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.

Issue Summary

Building with serverless results in an error:

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