Bug report

Describe the bug

When using React.Fragment like this:

import React from "react";

export default function Page() {
  const X = React.Fragment;
  return (
    <div>
      <style jsx global>{`
        html {
          margin: 0;
        }
      `}</style>
      <X>Hello</X>
    </div>
  );
}

You get this warning from React in the console:
``

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?

const query = {}
cosnt params = useParams() // returns {}
cosnt params = useParams('number') // returns {}
const param = useParam('key', "number") // returns NaN

1. I want to check param like if(param) but NaN will be true. It might not be useful.
2. Between useParams and param is not consistent, I'm a bit confusing.
3. Type implementati

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.

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 😄

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

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

Describe the bug

Hi there! 👋

I'm adding an origin of this form http://foo.s3-website-eu-west-1.amazonaws.com.

As other issues revealed those kind of origins are not an S3OriginConfig but a CustomOriginConfig.

So it might help to exclude these kind of origins, o

There is an import dependencie cycle between:

src/Interfaces/index.ts:
export * from '@Redux/IStore';

and

src/Redux/IStore.d.ts:
import { IHomePage } from '@Interfaces';

Eslint rule that detect the issue:
https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-cycle.md