Remix v3.0.0

Descripción Detallada

Pre-release Changes - BREAKING CHANGE: Middleware consumed through `remix/router` and `remix/fetch-router` must now explicitly continue the request chain by calling `next()` or return a `Response`. Middleware that returned `undefined` without calling `next()` now throws at runtime instead of implicitly continuing. Update context-loading middleware to return the downstream response: ```ts function loadUser(): Middleware { return (context, next) => { context.set(CurrentUser, user) return next() } } ``` - Improve Node compatibility for the `remix/assert` entrypoint. The default export is now callable as an alias for `assert.ok`, failure errors expose Node-style metadata, expected-error/message handling more closely follows `node:assert/strict`, strict/deep equality now handles `Object.is` and built-in object comparisons more consistently with Node, and `assert.partialDeepEqual` is available for strict partial deep comparisons. - Add `router.mount()` and the `RouteBuilder`/`RouteInstaller` types to `remix/router` and `remix/fetch-router` so larger apps can be built from smaller route groups without making feature modules hard-code their final URL. A feature module can now export a local route installer that registers routes like `/`, `/users/:id`, or a route map, and the parent can mount it at `/admin`, `/orgs/:orgId`, or another route pattern prefix while one router still owns request dispatch, matching, middleware, and default handling.