Why

• Remove webpackbar (which is broken) in favor of reusing the loading bar that we use for native.
• Remove useless info logs from webpack dev server
  • Of course, this adds a new warning that we can't appear to get rid of until updating: ⚠ ｢wds｣: transportMode is an experimental option, meaning its usage could potentially change without warning
• Make web warning specific to Webpack › Expo Webpack is in beta, and subject to breaking changes!
• Fix syntax errors and missing module errors -- making them a bit closer to Metro/native
• Fix webpack context (moved to [webpack] Use proper project context #3767)

Warnings

• Add support for bundling warnings (bundling_warning). In a project on web, import import getDevServer from "react-native/Libraries/Core/Devtools/getDevServer"; This will send an event: {"tag":"metro","id":1629222657834,"shouldHide":false,"type":"bundling_warning","warning":"./App.js 12:22-34\n\"export 'default' (imported as 'getDevServer') was not found in 'react-native/Libraries/Core/Devtools/getDevServer'"} which needs to be handled

Currently, warnings are handled as:

Compiled with warnings.
./node_modules/react-native/Libraries/Performance/Systrace.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

After

Test Plan

• expo start -w
• expo web

Have a project with a import 'missing' and a > where it's not supposed to be.