chore: update expo, ts and emotion

[dannyhw]

Issue:

What I did

I wanted to update expo, expo wanted to update typescript, typescript update broke emotion.

Emotion was already broken so I decided to finally fix and upgrade it.

This also adds a new package for exporting the theme and theme type which makes it easier to share in the repo

How to test

Please explain how to test your changes and consider the following questions

• run the example app

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
typescript	5.1.6	None	+0	40.1 MB	typescript-bot
@emotion/react	11.11.1	environment	+44	2.99 MB	emotion-release-bot
@emotion/native	11.11.0	None	+70	6.62 MB	emotion-release-bot
@react-native-async-storage/async-storage	1.17.11...1.18.2	None	+0/-0	408 kB	krizzu
react-native-web	0.18.12...0.19.6	None	+2/-4	3.02 MB	necolas
react-native-safe-area-context	4.5.0...4.6.3	None	+0/-213	237 kB	janicduplessis
@react-native-community/datetimepicker	6.7.3...7.2.0	None	+0/-0	211 kB	vonovak

🚮 Removed packages: [email protected], [email protected]

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: @react-native-community/[email protected]

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

[dannyhw]

@SocketSecurity ignore @react-native-community/[email protected]