Next

Describe the feature you'd like to request

I want to be able to initialize a Next.js app with the src directory.

It is currently a hassle to create the src on your own and move pages and other folders to it.

Describe the solution you'd like

Add an option to create-next-app to be able to do that. Like: --src, `

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

Description 📓

Currently the maxAge on the jwt and the expires on the cookie options are being set to a hard coded 15 minutes.

pkce

defined here

https://github.com/nextauthjs/next-auth/blob/e4ee520b4aba55fbc123801291bcba404f578d3f/packages/next-auth/src/core/lib/oauth/pkce-handler.ts#L7

set as expires here

https://github.com/nextauthjs/next-auth/blob/e4ee520b4aba55fbc12380129

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.