# Why
fix typecheck errors
fixes#70
# How
- fix nullable NavigationContainerRef from react-navigation
- for apollo-client, bun treats dependency differently for react-dom as
peerDependnecy from `@apollo/client`. to workaround this, i have to add
react-dom devDeps to the apollo plugin, so bun will keep the same
resolution
# Why
bun 1.3 uses isolated modules by default and then some errors happen
because of missing dependencies
# How
- add missing devDeps and peerDeps
- remove `**/webui/babel.config.js` to fix no `babel-preset-expo` as
dependencies. we don't need these default babel.config.js and can just
use the builtin from expo-cli
# Why
sdk 53 projects will pull eslint 9 by default. this pr tries to fix the
eslint 9 support.
# How
- update `[email protected]` to support eslint 9 base config
- add eslint 9 flat `eslint.config.js`
# Why
since `[email protected]` with the fix from
https://github.com/expo/expo/pull/36594, we don't need to disable
unstable_enablePackageExports anymore
# How
- [packages] remove `unstable_enablePackageExports` workaround. the
whole metro config can be removed
- [example] remove unused metro config and babel config
# Why
SDK 53 has a breaking change to devtools client transport. We have to
bump the version for dev-plugins packages
# How
- update packages to expo sdk 53
- fix typescript errors and lint errors
- apply workaround for antd:
https://github.com/expo/expo/discussions/36551#discussioncomment-13015890
# Why
migrate sdk 52
# How
- update deps to latest
- migrate from yarn to bun
- [mmkv] remove devDep to async-storage
- [react-navigation] the original
`@react-navigation/devtools/lib/module/useDevToolsBase` breaks because
of internal files that doesn't export in ESM mode. this pr tries to use
`useReduxDevToolsExtension` with an adapter to the redux extension
- [tinybase] migrate to 5.0
While testing devtools plugins, I found that I could not scroll when the
values were large or the lists of events were long. Tried adding
scrolling wherever I could create enough data that scrolling was needed:
- React Navigation: tested scrolling on list of events and state side
pane
- Apollo Client: testing scrolling on list of events and side pane
- React Query: tested scrolling on side pane. It looks like the list of
events has pagination, so scrolling may not be needed
- Tinybase: the entire web ui is an external component, so it likely
does not need this change
we may want to update again when we release the beta and full release,
so may not make sense to merge. I just wanted to test against canary and
create a video recording :)
# Why
since sdk 50 alpha includes the code changes we need, we can update sdk
50 and remove the patches
# How
- update `expo` version to `~50.0.0-alpha.7`
- remove patches
- since metro web on sdk 50 supports the `baseUrl`, we can migrate
webpack to metro web.
- remove the `mjs` from sourceExts that sdk 50 cli includes it already
Kudo Chien