Bump @remix-run/dev from 2.1.0 to 2.3.0

[dependabot]

Bumps @remix-run/dev from 2.1.0 to 2.3.0.

Release notes

Sourced from @​remix-run/dev's releases.

v2.3.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v230

v2.2.0

Minor Changes

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. (#7590)

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. (#10960)

• 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 useSumbit 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 (future.v3_fetcherPersist)

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. (#10962)

... (truncated)

Changelog

Sourced from @​remix-run/dev's changelog.

2.3.0

Patch Changes

• Support rendering of LiveReload component after Scripts in Vite dev (#7919)
• fix(vite): fix "react-refresh/babel" resolution for custom server with pnpm (#7904)
• Support JSX usage in .jsx files without manual React import in Vite (#7888)
• Support optional rendering of LiveReload component in Vite dev (#7919)
• Fix Vite production builds when plugins that have different local state between development and production modes are present, e.g. @mdx-js/rollup. (#7911)
• Cache resolution of Remix Vite plugin options (#7908)
• Support Vite 5 (#7846)
• Allow process.env.NODE_ENV values other than "development" in Vite dev (#7980)
• Attach CSS from shared chunks to routes in Vite build (#7952)
• fix(vite): Let Vite handle serving files outside of project root via /@fs (#7913)
  • This fixes errors when using default client entry or server entry in a pnpm project where those files may be outside of the project root, but within the workspace root.
  • By default, Vite prevents access to files outside the workspace root (when using workspaces) or outside of the project root (when not using workspaces) unless user explicitly opts into it via Vite's server.fs.allow.
• Improve performance of LiveReload proxy in Vite dev (#7883)
• fix(vite): deduplicate @remix-run/react (#7926)
  • Pre-bundle Remix dependencies to avoid Remix router duplicates.
  • Our remix-react-proxy plugin does not process default client and
  • server entry files since those come from within node_modules.
  • That means that before Vite pre-bundles dependencies (e.g. first time dev server is run) mismatching Remix routers cause Error: You must render this element inside a <Remix> element.
• Fix React Fast Refresh error on load when using defer in Vite dev server (#7842)
• Handle multiple "Set-Cookie" headers in Vite dev server (#7843)
• Fix flash of unstyled content on initial page load in Vite dev when using a custom Express server (#7937)
• Emit assets that were only referenced in the server build into the client assets directory in Vite build (#7892, cherry-picked in 8cd31d65)
• Populate process.env from .env files on the server in Vite dev (#7958)
• Fix FutureConfig type (#7895)
• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

2.2.0

Minor Changes

• Unstable Vite support for Node-based Remix apps (#7590)
  • remix build 👉 vite build && vite build --ssr
  • remix dev 👉 vite dev
  • Other runtimes (e.g. Deno, Cloudflare) not yet supported.
  • See "Future > Vite" in the Remix Docs for details
• Add a new future.v3_fetcherPersist flag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmounted in the UI, fetchers will persist until they return to an idle state (RFC) (#7704)
  • For more details, please refer to the React Router 6.18.0 release notes

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

Commits

• 38fb96f chore: Update version for release (#8031)
• 183468c chore: Update version for release (pre) (#8030)
• cd8261e chore: Update version for release (pre) (#8027)
• 8cd31d6 fix(remix-dev/vite): use ssrEmitAssets to support assets referenced by serv...
• d898629 chore: Update version for release (pre) (#8008)
• fffa5c4 Merge branch 'main' into release-next
• cf9b507 Stabilize useBlocker (#7882)
• 8eb9621 fix(remix-dev/vite): instantiate plugins independently for child compiler (#7...
• f2ccdd7 fix(vite): support Vite 5 (#7983)
• 9061b7d chore: format
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)