@vercel/remix - npm Package Versions

published 2.2.0 • last year

Changelog

v2.2.0

Date: 2023-10-31

What's Changed

Vite!

Remix 2.2.0 adds unstable support for Vite for Node-based apps! See our announcement blog post and the Future > Vite page in the Remix docs for more details.

You can try it out today with two new (unstable) templates:

# minimal server
npx create-remix@latest --template remix-run/remix/templates/unstable-vite

# custom server (Express example)
npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express

New APIs in @remix-run/dev
- unstable_vitePlugin: The new Remix Vite plugin
- unstable_createViteServer: Creates a Vite server in middleware mode for interop with custom servers
- unstable_loadViteServerBuild: Allows your custom server to delegate SSR requests to Vite during development
Changed APIs
- createRequestHandler: Now also allows the build argument to be a function that will be used to dynamically load new builds for each request during development
Other Runtimes
- Deno support is untested, but should work through Deno's Node/npm interop
- CloudFlare support is not yet available

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors:

You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
Form and useSubmit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
- <Form method="post" navigate={false} fetcherKey="my-key">
- submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })
- Invoking a fetcher in this way is ephemeral and stateless
- If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

Persistence Future Flag

Per the same RFC as above, we've introduced a new future.v3_fetcherPersist flag that allows you to opt-into the new fetcher persistence/cleanup behavior. Instead of being immediately cleaned up on unmount, fetchers will persist until they return to an idle state. This makes pending/optimistic UI much easier in scenarios where the originating fetcher needs to unmount.

This is sort of a long-standing bug fix as the useFetchers() API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an idle state
Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:
- Fetchers that complete while still mounted will no longer appear in useFetchers() after completion - they served no purpose in there since you can access the data via useFetcher().data
- Fetchers that previously unmounted while in-flight will not be immediately aborted and will instead be cleaned up once they return to an idle state
  - They will remain exposed via useFetchers while in-flight so you can still access pending/optimistic data after unmount
  - If a fetcher is no longer mounted when it completes, then it's result will not be post processed - e.g., redirects will not be followed and errors will not bubble up in the UI
  - However, if a fetcher was re-mounted elsewhere in the tree using the same key, then it's result will be processed, even if the originating fetcher was unmounted

Minor Changes

Unstable vite support (#7590)
New fetcher key APIs and navigate/fetcherKey params for navigational APIs (#10960)
New future.v3_fetcherPersist flag (#10962)

Patch Changes

@remix-run/express: Allow the Express adapter to work behind a proxy when using app.enable('trust proxy') (#7323)
- Previously, this used req.get('host') to construct the Remix Request, but that does not respect X-Forwarded-Host
- This now uses req.hostname which will respect X-Forwarded-Host
@remix-run/react: Fix warning that could be inadvertently logged when using route files with no default export (#7745)
create-remix: Support local tarballs with a .tgz extension which allows direct support for pnpm pack tarballs (#7649)
create-remix: Default the Remix app version to the version of create-remix being used (#7670)
- This most notably enables easier usage of tags, e.g. npm create remix@nightly

Updated Dependencies

Changes by Package

Full Changelog: v2.1.0...v2.2.0

2.1.0

published 2.1.0 • last year

Changelog

v2.1.0

Date: 2023-10-16

What's Changed

View Transitions

We're excited to release experimental support for the the View Transitions API in Remix! You can now trigger navigational DOM updates to be wrapped in document.startViewTransition to enable CSS animated transitions on SPA navigations in your application.

The simplest approach to enabling a View Transition in your Remix app is via the new <Link unstable_viewTransition> prop. This will cause the navigation DOM update to be wrapped in document.startViewTransition which will enable transitions for the DOM update. Without any additional CSS styles, you'll get a basic cross-fade animation for your page.

If you need to apply more fine-grained styles for your animations, you can leverage the unstable_useViewTransitionState hook which will tell you when a transition is in progress and you can use that to apply classes or styles:

function ImageLink(to, src, alt) {
  const isTransitioning = unstable_useViewTransitionState(to);
  return (
    <Link to={to} unstable_viewTransition>
      <img
        src={src}
        alt={alt}
        style={{
          viewTransitionName: isTransitioning ? "image-expand" : "",
        }}
      />
    </Link>
  );
}

You can also use the <NavLink unstable_viewTransition> shorthand which will manage the hook usage for you and automatically add a transitioning class to the <a> during the transition:

a.transitioning img {
  view-transition-name: "image-expand";
}

<NavLink to={to} unstable_viewTransition>
  <img src={src} alt={alt} />
</NavLink>

For an example usage of View Transitions, check out our fork of the Astro Records demo (which uses React Router but so does Remix 😉).

For more information on using the View Transitions API, please refer to the Smooth and simple transitions with the View Transitions API guide from the Google Chrome team.

Stable `createRemixStub`

After real-world experience, we're confident in the createRemixStub API and ready to commit to it, so in 2.1.0 we've removed the unstable_ prefix.

⚠️ Please note that this did involve 1 small breaking change - the <RemixStub remixConfigFuture> prop has been renamed to <RemixStub future> to decouple the future prop from a specific file location.

Minor Changes

Added unstable support for the View Transition API (#10916)
Stabilized the @remix-run/testing createRemixStub helper (#7647)

Patch Changes

Emulate types for JSON.parse(JSON.stringify(x)) in SerializeFrom (#7605)
- Notably, type fields that are only assignable to undefined after serialization are now omitted since JSON.stringify |> JSON.parse will omit them. See test cases for examples
- This fixes type errors when upgrading to v2 from 1.19
Avoid mutating meta object when tagName is specified (#7594)
Fix FOUC on subsequent client-side navigations to route.lazy routes (#7576)
Export the proper Remix useMatches wrapper to fix UIMatch typings (#7551)
@remix-run/cloudflare - sourcemap takes into account special chars in output file (#7574)
@remix-run/express - Flush headers for text/event-stream responses (#7619)

Updated Dependencies

Changes by Package

Full Changelog: v2.0.1...v2.1.0

2.0.1

published 2.0.1 • last year

Changelog

v2.0.1

Date: 2023-09-21

Patch Changes

Fix types for MDX files when using pnpm (#7491)
Update getDependenciesToBundle to handle ESM packages without main exports (#7272)
- Note that these packages must expose package.json in their exports field so that their path can be resolved
Fix server builds where serverBuildPath extension is .cjs (#7180)
Fix HMR for CJS projects using remix-serve and manual mode (remix dev --manual) (#7487)
- By explicitly busting the require cache, remix-serve now correctly re-imports new server changes in CJS
- ESM projects were already working correctly and are not affected by this.
Fix error caused by partially written server build (#7470)
- Previously, it was possible to trigger a reimport of the app server code before the new server build had completely been written. Reimporting the partially written server build caused issues related to build.assets being undefined and crashing when reading build.assets.version
Add second generic to UIMatch for handle field (#7464)
Fix resource routes being loaded through route.lazy (#7498)
Throw a semantically correct 405 ErrorResponse instead of just an Error when submitting to a route without an action (#7423)
Update to latest version of @remix-run/web-fetch (#7477)
Switch from crypto.randomBytes to crypto.webcrypto.getRandomValues for file session storage ID generation (#7203)
Use native Blob class instead of polyfill (#7217)

Changes by Package 🔗

Full Changelog: v2.0.0...v2.0.1

2.0.0

published 2.0.0 • last year

Changelog