What example does this report relate to?

blog-starter-typescript

What version of Next.js are you using?

10.0.4

What version of Node.js are you using?

14.15.4

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

next build / next dev

Describe the Bug

➜  blog-starter-typescript-app git:(mai

Sentry Issue: KAP-5KT

TypeError: Cannot read property '1' of null
  File "app:///main/utils/encoding.js", line 17, in getEncoding
    return /.*: Video: (.*?) \(.*/.exec(error.stderr)[1];

What do you want and why?

There is a queryKey property of the query hooks options, but looking at the source code it is not being utilized to set the query key. My problem is that for one of my queries the query key changes often due to user input (sorting and filtering), and I would like a query key I set so that I can fetch from the cache easier on other pages.

Possible implement

Summary

Some screen plugins need a different UI than a sidebar or a popup. It would be nice to get all of the ergonomic benefits of a screen, w/o needing to use the Tina sidebar UI or popup UI.

Without all the marketing.

Summary of proposed feature
There is some confusion about how refreshing tokens can happen or what expiration means in the context of next-auth and a given provider. This probably stems from that users simply expect the access token to be always up-to-date when used. We don't currently support automatic access token refreshing, but it CAN be implemented by the users. Until we have built-in

In the cart section, the number of items doesn't alter the total sum of the purchase.

Awesome work guys, I can take this issue if you want 😄

Hi! First off, thank you so much for this library!

I noticed some unexpected behavior (not sure if it's a bug or intended) when using DefaultSeo and NextSeo. The DefaultSeo og:title and og:description meta tags are not overridden by NextSeo's title and description configurations unless an openGraph configuration object is provided to NextSeo. I believe this is due to http

Some folks have noted it would be beneficial to have this repository translated to other languages. One contributor has already volunteered to translate the repository into Russian (woohoo!).

If anyone has the time and drive to help out with other languages, please reply below with the proposed language and I'll give you the "go-ahead"... just to make sure two people don't create translations i

Is your feature request related to a problem? Please describe.

Currently both lambdas can only have the same arn role (if set). However it would be better to follow the same approach that there is for the name field

  roleArn:
      defaultLambda: arn
      apiLambda: arn

The reason I say this is because I wouldn't want to give the defaultLambda access to the database.