remix v3.0.0-rc.4

Pre-release Changes

• BREAKING CHANGE: Configure the application-wide router context by augmenting the new type-only remix root module. Runtime APIs remain available through remix/* subpath imports. Apps that use @remix-run/fetch-router directly should continue to augment that module.

  -declare module 'remix/router' {
  +declare module 'remix' {
     interface RouterTypes {
       context: AppContext
     }
   }

• BREAKING CHANGE: remix/fetch-proxy now returns upstream redirects by default so stable development proxies preserve redirect responses and session cookies at the browser boundary. Pass redirect: 'follow' to preserve the previous behavior.

• Customize transformed-file caching in remix/assets with a FileCache or the configurable createFsFileCache() filesystem LRU. Existing FileStorage configurations remain compatible, and caching stays disabled unless configured (see #11859).

• Optimize named imports through eligible side-effect-free barrel files in remix/assets.

• remix/ui now supports data-rmx-preserve-attrs to keep named client-owned attributes, such as a root theme attribute, across frame reloads while updating the rest of the element (see #11809).

• Generated import maps now include dependencies used by the configured HMR module importer, so its bare imports resolve even when they are not also used by the app's browser entry.

• Improve browser HMR for transitive dependency updates

• Cookie options exposed through remix/cookie now accept lowercase sameSite values such as 'lax', matching the authentication and session examples.

• Remix server entrypoints can pass router.fetch directly to createRequestListener() without client metadata being treated as RequestInit.

• Publish the in-progress guide chapters with an unfinished notice and links to relevant package READMEs. Installed guides and READMEs link to bundled README mirrors instead of hosted documentation (see #11920).

• Declare which remix entry points have side effects based on their owning packages.

• remix/ui-hmr now preserves hoisted function declarations written after a component's render return, so valid closures continue to work in browser development builds.

• Align frame identification and named targeting in the default browser resolver with server-side rendering, including top-frame navigation and reloads. Browser frame requests also report server rendering errors through render()'s configured error handler or default reporter (see #11941).

• Allow client entry props to use ordinary interfaces, including nested objects whose properties are all optional (see #11918).

• Bumped @remix-run/* dependencies:

  • assert@0.3.1
  • assets@0.8.0
  • async-context-middleware@0.3.8
  • auth@0.3.3
  • auth-middleware@0.2.8
  • cli@0.8.0
  • compression-middleware@0.1.16
  • cookie@0.7.1
  • cop-middleware@0.1.11
  • cors-middleware@0.2.1
  • csrf-middleware@0.2.0
  • fetch-proxy@0.9.0
  • fetch-router@0.22.2
  • file-storage@0.13.8
  • file-storage-s3@0.1.6
  • form-data-middleware@0.3.8
  • form-data-parser@0.17.7
  • fs@0.4.7
  • headers@0.21.3
  • html-template@0.3.2
  • lazy-file@5.0.7
  • logger-middleware@0.3.8
  • method-override-middleware@0.1.16
  • mime@0.4.3
  • multipart-parser@0.16.6
  • multiple-import-maps-polyfill@0.1.1
  • node-fetch-server@0.14.2
  • node-hmr@0.2.1
  • node-tsx@0.1.2
  • render-middleware@0.3.2
  • response@0.3.10
  • route-pattern@0.25.0
  • session@0.4.3
  • session-middleware@0.5.1
  • session-storage-memcache@0.1.3
  • session-storage-redis@0.1.2
  • spa@0.1.3
  • static-middleware@0.4.17
  • tar-parser@0.8.1
  • terminal@0.1.2
  • test@0.6.2
  • ui@0.11.0
  • ui-hmr@0.1.1