# @uppy/react's new useUppyState breaking support for React 16/17?

**URL:** <https://community.transloadit.com/t/uppy-reacts-new-useuppystate-breaking-support-for-react-16-17/16887>\
**Category:** Uppy\
**Created:** [November 9, 2023, 8:57am UTC](https://community.transloadit.com/t/uppy-reacts-new-useuppystate-breaking-support-for-react-16-17/16887 "2023-11-09T08:57:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaffekoppen](https://avatars.discourse-cdn.com/v4/letter/k/90ced4/32.png) [@kaffekoppen](https://community.transloadit.com/u/kaffekoppen)\
**Post date:** [November 9, 2023, 8:57am UTC](https://community.transloadit.com/t/uppy-reacts-new-useuppystate-breaking-support-for-react-16-17/16887/1 "2023-11-09T08:57:19Z")

</div>

Hi, I’m using React 16.14.0, and I assume React 16 should work with Uppy since React 16 it is a peerDependency?

I get the following error from Webpack after upgrading `@uppy/react` to `3.2.0` (latest).

```auto

ERROR in ./node_modules/@uppy/react/lib/useUppyState.js 5:9-29
export 'useSyncExternalStore' (imported as 'useSyncExternalStore') was not found in 'react' (possible exports: Children, Component, Fragment, Profiler, PureComponent, StrictMode, Suspense, __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED, cloneElement, createContext, createElement, createFactory, createRef, forwardRef, isValidElement, lazy, memo, useCallback, useContext, useDebugValue, useEffect, useImperativeHandle, useLayoutEffect, useMemo, useReducer, useRef, useState, version)
 @ ./node_modules/@uppy/react/lib/index.js 8:0-60 8:0-60

```

It seems that `useSyncExternalStore` is not available before React 18.

I’m using `DashboardModal` from `@uppy/react`.

Edit: reproduction is here: [https://codesandbox.io/p/sandbox/stoic-easley-g6lstz](https://codesandbox.io/p/sandbox/stoic-easley-g6lstz)  
Opened an issue here: [@uppy/react's new useUppyState breaking support for React 16/17? · Issue #4783 · transloadit/uppy · GitHub](https://github.com/transloadit/uppy/issues/4783)

Previously: Couldn’t reproduce the issue in Codesandbox using Parcel, and was hoping someone else also has this issue before I try to reproduce with a webpack setup. Since it’s not an issue in Parcel, I figured it might be something else I’m doing wrong?