chore: Update version for release

[remix-run-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.

Releases

@remix-run/architect@2.0.0

Minor Changes

• Importing functions and types from the remix package is deprecated, and all (#3284)
  exported modules will be removed in the next major release. For more details,
  see the release notes for 1.4.0
  where these changes were first announced.

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.0.0

@remix-run/cloudflare@2.0.0

Minor Changes

• Importing functions and types from the remix package is deprecated, and all (#3284)
  exported modules will be removed in the next major release. For more details,
  see the release notes for 1.4.0
  where these changes were first announced.

Patch Changes

• Updated dependencies:
  • @remix-run/server-runtime@2.0.0

@remix-run/dev@2.0.0

Minor Changes

• Added support for a new route meta API to handle arrays of tags instead of an object. For details, check out the RFC. (#4610)

Patch Changes

• Added support for feature flags in remix.config.js (#4566)

• Replace migrations with codemods. Specifically, npx @remix-run/dev migrate is now @remix-run/dev codemod. (#4572)

  Under the hood, codemods are now written via Babel's Visitor API instead of jscodeshift.
  Also replace-remix-magic-imports is now faster as it no longer depends on a network connection
  and does not incur the overhead of spinning up workers for jscodeshift.

• bump esbuild to fix an issue with spreading props followed by a key as well as a jsx name collision edge case when using packages with the name react in them, like @remix-run/react. (#4301)

  it also utilizies esbuild's native yarn pnp compatibility instead of using @yarnpkg/esbuild-plugin-pnp

• Updated dependencies:

  • @remix-run/server-runtime@2.0.0
  • @remix-run/serve@2.0.0

@remix-run/node@2.0.0

Minor Changes

• Importing functions and types from the remix package is deprecated, and all (#3284)
  exported modules will be removed in the next major release. For more details,
  see the release notes for 1.4.0
  where these changes were first announced.

Patch Changes

• chore: update @remix-run/web-fetch to 4.3.2 (#4644)

  • fix: Memory leak caused by unregistered listeners. Solution was copied from a node-fetch pr.
  • fix: Add support for custom "credentials" value. Nothing is done with them at the moment but they pass through for the consumer of the request to access if needed.

• Updated dependencies:

  • @remix-run/server-runtime@2.0.0

@remix-run/react@2.0.0

Minor Changes

• Importing functions and types from the remix package is deprecated, and all (#3284)
  exported modules will be removed in the next major release. For more details,
  see the release notes for 1.4.0
  where these changes were first announced.
• Added support for a new route meta API to handle arrays of tags instead of an object. For details, check out the RFC. (#4610)

Patch Changes

• Ensure route modules are loaded even in failure cases. (#4611)

  This addresses a long standing issue where you would end up in your root catch boundary if a form transition to another route threw. This no longer occurs and you end up in the contextual boundary you'd expect.

  Fixed in PR feat(remix-server-runtime): RRR 1.3 / 1.4 - handleDocumentRequest #4385

@remix-run/server-runtime@2.0.0

Minor Changes

• We have been busy at work Layering Remix on top of React Router 6.4 and are excited to be releasing the step 1 in this process that consists of running the server flow through a local copy the new framework agnostic @remix-run/router. (#4612)
• Importing functions and types from the remix package is deprecated, and all (#3284)
  exported modules will be removed in the next major release. For more details,
  see the release notes for 1.4.0
  where these changes were first announced.
• Added support for a new route meta API to handle arrays of tags instead of an object. For details, check out the RFC. (#4610)

Patch Changes

• fix: Properly categorize internal framework-thrown error Responses as error boundary errors (#4385)

  Previously there was some ambiguity around "thrown Responses go to the CatchBoundary".
  The CatchBoundary exists to give the user a place to handle non-happy path code flows
  such that they can throw Response instances from their own code and handle them in a
  CatchBoundary. However, there are a handful of framework-internal errors that make
  sense to have a non-500 status code, and the fact that these were being thrown as Responses
  was causing them to go into the CatchBoundary, even though they were not user-thrown.

  With this change, anything thrown by the framework itself (Error or Response) will
  go to the ErrorBoundary, and any user-thrown Response instances will go to the
  CatchBoundary. Thereis one exception to this rule, which is that framework-detected
  404's will continue to go to the CatchBoundary since users should have one single
  location to handle 404 displays.

  The primary affected use cases are scenarios such as:

  • HTTP OPTIONS requests (405 Unsupported Method )
  • GET requests to routes without loaders (400 Bad Request)
  • POST requests to routes without actions (405 Method Not Allowed)
  • Missing route id in _data parameters (403 Forbidden)
  • Non-matching route id included in _data parameters (403 Forbidden)

create-remix@2.0.0

Patch Changes

• Updated dependencies:
  • @remix-run/dev@2.0.0

remix@2.0.0

Patch Changes

• Replace references to the old migrate command with the new codemod command (#4646)

• Replace migrations with codemods. Specifically, npx @remix-run/dev migrate is now @remix-run/dev codemod. (#4572)

  Under the hood, codemods are now written via Babel's Visitor API instead of jscodeshift.
  Also replace-remix-magic-imports is now faster as it no longer depends on a network connection
  and does not incur the overhead of spinning up workers for jscodeshift.

• chore: update @remix-run/web-fetch to 4.3.2 (#4644)

  • fix: Memory leak caused by unregistered listeners. Solution was copied from a node-fetch pr.
  • fix: Add support for custom "credentials" value. Nothing is done with them at the moment but they pass through for the consumer of the request to access if needed.

• bump esbuild to fix an issue with spreading props followed by a key as well as a jsx name collision edge case when using packages with the name react in them, like @remix-run/react. (#4301)

  it also utilizies esbuild's native yarn pnp compatibility instead of using @yarnpkg/esbuild-plugin-pnp

See the CHANGELOG.md in individual Remix packages for all changes.

@remix-run/cloudflare-pages@2.0.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.0.0

@remix-run/cloudflare-workers@2.0.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.0.0

@remix-run/deno@2.0.0

Patch Changes

• Updated dependencies:
  • @remix-run/server-runtime@2.0.0

@remix-run/eslint-config@2.0.0

Patch Changes

• Replace references to the old migrate command with the new codemod command (#4646)

@remix-run/express@2.0.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.0.0

@remix-run/netlify@2.0.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.0.0

@remix-run/serve@2.0.0

Patch Changes

• Updated dependencies:
  • @remix-run/express@2.0.0

@remix-run/vercel@2.0.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.0.0