🚀 Feature request

Current Behavior

The type ErrorMessage doesn't have an id property.

Desired Behavior

It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.

Suggested Solution

Add id={this.props.id} to the outer component in ErrorMessage.

Who does this impact? Who is this

Describe the bug
The following PR introduced some breaking change in typings: https://github.com/beautifulinteractions/beautiful-react-hooks/pull/156/files#diff-b52768974e6bc0faccb7d4b75b162c99R19

Argument of type '() => void' is not assignable to parameter of type 'any[]'.
  Type '() => void' is missing the following properties from type 'any[]': pop, push, concat, join, and 27 more

I'm trying to automate the interaction with WindowsTerminal. It seems to be a UWP application, which I have no idea how to start such application directly using Application().start. I've tried to locate it using Desktop, but got quite confused..

Any help on this?

It's important, I think, if the goal is to communicate that this can replace React in more ways than function.

Description

Graphql clients comparison (apollo client vs graphql-hooks vs urql).

Suggested implementation

List describing the advantages / disadvantages to other major clients. This library looks interesting but I don't see any advantage other file size.

Now we have 3 binaries in npm and script which run necessary binary depends on the current platform.

There are 2 big problems with current behavior:

1. npm package size is huge (26 MB)
2. Node.js startup time is not great.

Solution:

1. postinstall script download necessary binary (many npm packages use this approac