[BUGFIX] Objects are not valid as a React child (found object with keys {children} ) **Runtime Error**

[gaabgonca]

Problem
When introducing children to DatePicker, Next.js throws the following runtime error

How to reproduce

• Run the demo app provided in this repository
• Update pages>index.tsx so that the DatePicker component is not self-closing but has children
• A simple <div/> is sufficient to get the bug. Like this:

<DatePicker show={show} setShow={(state) => setShow(state)} options={options} classNames="absolute" >
	<div/>
</DatePicker>

Root cause
The ReactNode as the type of children prop was too broad. This caused children to be identified as an object/ any type making React unable to render it. This was fixed in React 18.

Solution
Narrow down the type of children to ReactElement and destructure it when used.

Extra
Code provided in README.md was missing parenthesis on useState<boolean>(false) call, thus disabling blind copy-pasting. That was fixed too.

Changes made

• Update usages of ReactNode with ReactElement
• Add missing parenthesis on README.md
• Update DatePicker children rendering logic

[OMikkel]

This PR has been merged 😃

[diecodev]

This bug is still happen. Pls Fix it.