chore: reduce unused web code (#24294)

# Why

Web bundles are too big by default, this is one of a series of PRs that
will reduce code that is pulled in on web.

<!--
Please describe the motiv

chore: reduce unused web code (#24294)

# Why

Web bundles are too big by default, this is one of a series of PRs that
will reduce code that is pulled in on web.

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

Because we compile the src of `@expo/metro-runtime` to CJS, the
`react-native-web` shaking plugin breaks and we import everything. This
PR also switches the input for `@expo/metro-runtime` to be `src` for
both web and native, while using `build` for Node.js and types.

<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

feat(metro-runtime): Production bundle splitting runtime for web (#24291)

# Why

- Split out of the bundle splitting branch. These changes ensure that
the code fetching end evaluation logic is in

feat(metro-runtime): Production bundle splitting runtime for web (#24291)

# Why

- Split out of the bundle splitting branch. These changes ensure that
the code fetching end evaluation logic is included in production apps
web apps.
- Also reduces use of `react-native-web` for simplicity and sanity.


<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

migrate expo-router to expo/expo (#23725)

# Why

Migrate expo-router to expo/expo from expo/router so we can version it
with the Expo SDK. Also required for further integration with Expo CLI,
ex

migrate expo-router to expo/expo (#23725)

# Why

Migrate expo-router to expo/expo from expo/router so we can version it
with the Expo SDK. Also required for further integration with Expo CLI,
expo-font, expo-image, etc.

# How

- Migrate `expo-router`, and `@expo/metro-runtime`.
- Fold `expo-head` into `expo-router`.
- Integrate in `apps/sandbox` for low-stakes testing. Another PR can
pull in.

# Test Plan

- `apps/sandbox` starts on all platforms and pulls from expo-router in
the `packages` directory.
<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...