fix: prevent unnecessary wrapping of single line jsx elements (#2183)
When having a single line statement with an import statement everything works as expected.
```jsx
    import * as React from "react";
    <ReactComponent />;
```
However if you remove the import statement, a semicolon `;` appears in the output. We no longer need the explicit import statements as this can be configured globally, and we have an eslint rule requiring us to close every js statement with a semicolon.
```jsx
    <ReactComponent />;
```
This happens because of the fix/changes done in this issue: #842, which causes every statement starting with JSX to be wrapped in a Fragment. This will cause the semicolon to be added inside the Fragment, and cause it to be rendered.
This change causes the examples to only be wrapped in a Fragment if multiple jsx statements are returned on root level of the example by checking for the error before wrapping.
Co-authored-by: Thomas Roest <thomas.roest@moxio.com>

fix: replace deprecated defaultProps

fix: remove some unnecessary ignores (#2160)
Co-authored-by: Thomas Roest <thomas.roest@moxio.com>

fix: update peer deps (#2125)
Co-authored-by: Thomas Roest <thomas.roest@moxio.com>

feat: upgrade types and create release React 18 upgrade (#2124)
310b08a
Co-authored-by: Thomas Roest <thomas.roest@moxio.com>

Upgrade to React 18 (#2087) (#2110)
Upgrade to React 18
* replace ReactDOM.render with createRoot in index.ts
* fix new TS errors after upgrading @types
* replace ReactDOM.render in Preview.tsx
* replace ReactDOM.unmountComponentAtNode with root.unmount()
* remove ReactDOM import
* upgrade react testing library
* replace deprecated React.SFC type with React.FC
DefinitelyTyped/DefinitelyTyped#30364
* Fix TS errors in propTypes.children
propTypes.node results in TS errors. There doesn't seem to be a good alternative ( other than making the children propTypes more strict, which could result more errors)
Instead use something less restrictive (propTypes.any) for children and components.
* fix TS errors, extract props interfaces with children
* fix TS errors, add context types
* TS fix
* Fix React unmount error
Unmount asynchronously with setTimout
https://stackoverflow.com/questions/73459382/react-18-async-way-to-unmount-root
error message:
Warning: Attempted to synchronously unmount a root while React was already rendering. React cannot finish unmounting the root until the current render has completed, which may lead to a race condition.
* make wrapper unmount test async
---------
Co-authored-by: Thomas Roest <thomas.roest@moxio.com>

Upgrade to React 17 (#2037)
* upgrade react core depedencies to React 17
* Upgrade react-simple-code-editor and remove enzyme react 16 adapter
* replace enzyme adapter react
* Fix: fix failing Editor test
* Chore: update dependencies in examples/basic
BREAKING CHANGE:
React 16 no longer supported

fix: ensure devserver client options are configurable (#2034)
* fix: ensure devserver client options are configurable
When a custom `webpackConfig.devServer.client` option is set, they are
currently being overridden by the `baseConfig.client` field.
Ensure that field is extendible by consumers while also ensuring the
base config values stay fixed.
#2033
* fix: ensure all devServer options are overridable; add tests

feat: Upgrade to Webpack 5 (#1996)
This is a start for upgrading to webpack 5 and webpack-dev-server ^4. With these changes, the basic examples are working ( incl. hot module reloading ). But there are more todo's left
* update dev-server config
* make StyleguidistOptionsPlugin.ts work with webpack 5 and fix test
* fix make-webpack-config.spec.ts tests
* upgrade other webpack loader dependencies to latests versions (optional?)
* fix type errors
* fix deprecation warnings
Fixes #1932
BREAKING CHANGE:
Webpack 4 is no longer supported.

feat: Webpack 5 support (#1903)
* Upgrade react-dev-utils to latest version v12 (supports Webpack 5)
* Fix Webpack example for local testing
* Upgrade webpack related dependencies for maintenance: webpack, webpack-cli, and webpack-dev-server
* Remove unnecessary Webpack configuration around Hot Module Replacement. webpack-dev-server should automatically inject HMR related configurations already
Closes #1703
Closes #1864
Closes #1740
Closes #1822
Closes #1786