Next

Describe the feature you'd like to request

Currently uses AmplifyAuthenticator which is legacy. Also using an older verison of @aws-amplify/ui-react & aws-amplify

Describe the solution you'd like

Should be using the new Authenticator componet

Describe alternatives you've considered

Keep using the old one until is deprecated

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

• auth
• custom-server
• cypress
• fauna
• i18n-next-rosetta
• no-prisma
• plain-js
• static
• store

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:

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.