[C3] Bump create-remix from 2.1.0 to 2.2.0 in /packages/create-cloudflare/src/frameworks

[dependabot]

Bumps create-remix from 2.1.0 to 2.2.0.

Release notes

Sourced from create-remix's releases.

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)

• 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:

... (truncated)

Changelog

Sourced from create-remix's changelog.

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

Patch Changes

• Support local tarballs with .tgz extension, which allows direct support for pnpm pack tarballs (#7649)
• Set default Remix version to match the version of create-remix being used (#7670)
  • This most notably enables easier usage of tags, e.g. npm create remix@nightly

Commits

• 85caf9b chore: Update version for release (#7841)
• 23bf4c8 chore: Update version for release (pre) (#7839)
• ccc77f5 chore: Update version for release (pre) (#7831)
• 754d6b8 chore: Update version for release (pre) (#7827)
• 4841b62 chore: Update version for release (pre) (#7813)
• aa8511e chore: Update version for release (pre) (#7780)
• bf2604c fix(create-remix): default Remix version to CLI version (#7670)
• 521e272 Merge branch 'release-next' into dev
• 1f5b740 Fix: using a local *.tgz stack (#7649)
• See full diff 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)

[dependabot]

The following labels could not be found: dependencies.

[changeset-bot]

🦋 Changeset detected

Latest commit: fa53a5a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
create-cloudflare	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6718886294/npm-package-wrangler-4316

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6718886294/npm-package-wrangler-4316

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6718886294/npm-package-wrangler-4316 dev path/to/script.js

Additional artifacts:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6718886294/npm-package-cloudflare-pages-shared-4316

Note that these links will no longer work once the GitHub Actions artifact expires.

---

wrangler@3.15.0 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	3.20231025.0	3.20231025.0
workerd	1.20231025.0	1.20231025.0
workerd --version	1.20231025.0	2023-10-25

|

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[codecov]

Codecov Report

Merging #4316 (fa53a5a) into main (a1c9f43) will increase coverage by 0.04%.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #4316      +/-   ##
==========================================
+ Coverage   75.34%   75.38%   +0.04%     
==========================================
  Files         223      223              
  Lines       12341    12341              
  Branches     3190     3190              
==========================================
+ Hits         9298     9303       +5     
+ Misses       3043     3038       -5     

see 4 files with indirect coverage changes