🚀 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?

Describe the bug
The sidebar has overflow: scroll causing scrollbars always to be visible on Windows

To Reproduce
Steps to reproduce the behavior:

1. Go to documentation using Windows

Expected behavior
There should not be scrollbars before the content overflows

Screenshots
![image](https://user-images.githubusercontent.com/2255960/99193174-891e7c00-2777-11eb-8ceb-79

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