chore: Update version for release (pre)

[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.

⚠️⚠️⚠️⚠️⚠️⚠️

release-next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on release-next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@remix-run/dev@2.0.0-pre.0

Minor Changes

• allow defining multiple routes for the same route module file (#3970)

Patch Changes

• Support Typescript 4.9 features (like satisfies) in Remix app/ code (#4754)

  esbuild 0.15.13 added support for parsing TS 4.9 satisfies, so upgrading to esbuild 0.16.3 adds that ability to the Remix compiler

• Optimize parentRouteId lookup in defineConventionalRoutes (#4800)

  Local runs of production Remix builds:

  • Realistic project w/ 700 routes: 10-15s -> <1s (>10x faster)
  • Example project w/ 1,111 routes: 27s -> 0.104s (259x faster)

• Convention for Remix optional segments (#4706)

  Note that this only set ups the convention conversion for React Router.
  Optional segments won't be available in Remix until Remix is built on top of React Router v6.5

  Converts segments surrounded by parenthesis into optional segments for React Router.
  For example /($lang)/about will be converted to /:lang?/about in React Router.

  This means /($lang)/about would match:

  /en/about
  /fr/about
  /about
  

  Another example: /(one)/($two)/(three).($four) route would match all of the following:

  /
  /one
  /one/param1
  /one/param1/three
  /one/param1/three/param2
  

• fixes a bug in ts -> js conversion on windows by using a relative unix style path as fast-glob uses unix style paths (#4718)

• Updated dependencies:

  • @remix-run/serve@2.0.0-pre.0
  • @remix-run/server-runtime@2.0.0-pre.0

create-remix@2.0.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/dev@2.0.0-pre.0

remix@2.0.0-pre.0

Patch Changes

• Support Typescript 4.9 features (like satisfies) in Remix app/ code (#4754)

  esbuild 0.15.13 added support for parsing TS 4.9 satisfies, so upgrading to esbuild 0.16.3 adds that ability to the Remix compiler

• Fix TypedResponse so that Typescript correctly shows errors for incompatible types in loaders and actions. (#4734)

  Previously, when the return type of a loader or action was explicitly set to TypedResponse<SomeType>,
  Typescript would not show errors when the loader or action returned an incompatible type.

  For example:

  export const action = async (
    args: ActionArgs
  ): Promise<TypedResponse<string>> => {
    return json(42);
  };

  In this case, Typescript would not show an error even though 42 is clearly not a string.

  This happens because json returns a TypedResponse<string>,
  but because TypedReponse<string> was previously just Response & { json: () => Promise<string> }
  and Response already defines { json: () => Promise<any> }, type erasure caused Promise<any> to be used for 42.

  To fix this, we explicitly omit the Response's json property before intersecting with { json: () => Promise<T> }.

• Optimize parentRouteId lookup in defineConventionalRoutes (#4800)

  Local runs of production Remix builds:

  • Realistic project w/ 700 routes: 10-15s -> <1s (>10x faster)
  • Example project w/ 1,111 routes: 27s -> 0.104s (259x faster)

• adds a new testing package to allow easier testing of components using Remix specific apis like useFetcher, useActionData, etc. (#4539)

• fixes a bug in ts -> js conversion on windows by using a relative unix style path as fast-glob uses unix style paths (#4718)

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

@remix-run/architect@2.0.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.0.0-pre.0

@remix-run/cloudflare@2.0.0-pre.0

Patch Changes

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

@remix-run/cloudflare-pages@2.0.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.0.0-pre.0

@remix-run/cloudflare-workers@2.0.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.0.0-pre.0

@remix-run/deno@2.0.0-pre.0

Patch Changes

• Fix types for request handler context (#4715)
• Updated dependencies:
  • @remix-run/server-runtime@2.0.0-pre.0

@remix-run/express@2.0.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.0.0-pre.0

@remix-run/netlify@2.0.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.0.0-pre.0

@remix-run/node@2.0.0-pre.0

Patch Changes

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

@remix-run/react@2.0.0-pre.0

Patch Changes

• Update @remix-run/react to use Router from react-router-dom@6.4.4 (#4731)

• Allow pass-through props to be passed to the script rendered by ScrollRestoration (#2879)

• adds a new testing package to allow easier testing of components using Remix specific apis like useFetcher, useActionData, etc. (#4539)

• Fixed a problem with live reload and firefox infinitely reloading the page (#4725)

  The problem is:

  1. Firefox is calling ws.onclose immediately upon connecting (?!)
  2. Then we’re trying to reconnect, and upon reconnection, we reload the page.
  3. Firefox then calls ws.onclose again after reconnecting and the loop starts over

  This fix is to check event.code === 1006 before actually trying to reconnect and the reload the page. 1006 means the connection was closed abnormally (https://www.rfc-editor.org/rfc/rfc6455#section-7.4.1). In our case, that means the server was shut down in local dev and then the socket can reconnect again when the server is back up.

  It’s unclear to me why Firefox is calling onclose immediately upon connecting to the web socket, but it does.

@remix-run/serve@2.0.0-pre.0

Patch Changes

• Fix TypedResponse so that Typescript correctly shows errors for incompatible types in loaders and actions. (#4734)

  Previously, when the return type of a loader or action was explicitly set to TypedResponse<SomeType>,
  Typescript would not show errors when the loader or action returned an incompatible type.

  For example:

  export const action = async (
    args: ActionArgs
  ): Promise<TypedResponse<string>> => {
    return json(42);
  };

  In this case, Typescript would not show an error even though 42 is clearly not a string.

  This happens because json returns a TypedResponse<string>,
  but because TypedReponse<string> was previously just Response & { json: () => Promise<string> }
  and Response already defines { json: () => Promise<any> }, type erasure caused Promise<any> to be used for 42.

  To fix this, we explicitly omit the Response's json property before intersecting with { json: () => Promise<T> }.

• adds a new testing package to allow easier testing of components using Remix specific apis like useFetcher, useActionData, etc. (#4539)

• Updated dependencies:

  • @remix-run/express@2.0.0-pre.0

@remix-run/server-runtime@2.0.0-pre.0

Patch Changes

• Fix TypedResponse so that Typescript correctly shows errors for incompatible types in loaders and actions. (#4734)

  Previously, when the return type of a loader or action was explicitly set to TypedResponse<SomeType>,
  Typescript would not show errors when the loader or action returned an incompatible type.

  For example:

  export const action = async (
    args: ActionArgs
  ): Promise<TypedResponse<string>> => {
    return json(42);
  };

  In this case, Typescript would not show an error even though 42 is clearly not a string.

  This happens because json returns a TypedResponse<string>,
  but because TypedReponse<string> was previously just Response & { json: () => Promise<string> }
  and Response already defines { json: () => Promise<any> }, type erasure caused Promise<any> to be used for 42.

  To fix this, we explicitly omit the Response's json property before intersecting with { json: () => Promise<T> }.

• • Ensure loader request's proxy headers on document action submissions (#4829)
  • Fix an issue where loader request's reflected method: "POST" on document submissions

• adds a new testing package to allow easier testing of components using Remix specific apis like useFetcher, useActionData, etc. (#4539)

• Fix error boundary tracking for multiple errors bubbling to the same boundary (#4829)

@remix-run/testing@2.0.0-pre.0

Patch Changes

• adds a new testing package to allow easier testing of components using Remix specific apis like useFetcher, useActionData, etc. (#4539)
• Updated dependencies:
  • @remix-run/react@2.0.0-pre.0
  • @remix-run/server-runtime@2.0.0-pre.0
  • @remix-run/node@2.0.0-pre.0

@remix-run/vercel@2.0.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.0.0-pre.0

@remix-run/eslint-config@2.0.0-pre.0

[brophdawg11]

seems we still have the changesets issue where a minor changeset results in a major version bump 😕