Remix 3.0.0 ships its internal packages at 1.0.0 and renames @remix-run/ui to @remix-run/component. The Remix 3 orchestrion config only matches the 0.x release candidate packages, so on 3.0.0 none of the hooks apply, and nothing warns:
createRouter (@remix-run/fetch-router): http.server spans are named GET instead of the route pattern
createAssetServer (@remix-run/assets): browser modules get no debug IDs
createRequestListener (@remix-run/node-fetch-server): errors outside a router are not captured
run (@remix-run/component): component render errors are not captured
File paths and function names are unchanged in 1.0.0. Affects @sentry/remix 11.2.0 and 11.3.0 with remix@3.0.0.
Related: #23901, #24679
Remix 3.0.0 ships its internal packages at 1.0.0 and renames
@remix-run/uito@remix-run/component. The Remix 3 orchestrion config only matches the 0.x release candidate packages, so on 3.0.0 none of the hooks apply, and nothing warns:createRouter(@remix-run/fetch-router):http.serverspans are namedGETinstead of the route patterncreateAssetServer(@remix-run/assets): browser modules get no debug IDscreateRequestListener(@remix-run/node-fetch-server): errors outside a router are not capturedrun(@remix-run/component): component render errors are not capturedFile paths and function names are unchanged in 1.0.0. Affects
@sentry/remix11.2.0 and 11.3.0 withremix@3.0.0.Related: #23901, #24679