Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update version for release #4893

Merged
merged 1 commit into from
Dec 16, 2022

Conversation

remix-run-bot
Copy link
Contributor

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/dev@1.9.0

Minor Changes

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

  • Added support and conventions for optional route segments (#4706)

    Routes surrounded by parenthesis will be converted 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
    

    As with any of our conventions, you can escape this conversion by wrapping the route filename in square brackets. For example, /[(one)]/two would match the URL path /(one)/two.

Patch Changes

  • The Remix compiler now supports new Typescript 4.9 syntax (like the satisfies keyword) (#4754)
  • Optimize parentRouteId lookup in defineConventionalRoutes. (#4800)
  • Fixed a bug in .ts -> .js conversion on Windows by using a relative unix-style path (#4718)
  • Updated dependencies:
    • @remix-run/server-runtime@1.9.0

create-remix@1.9.0

Patch Changes

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

remix@1.9.0

Patch Changes

  • The Remix compiler now supports new Typescript 4.9 syntax (like the satisfies keyword) (#4754)

  • Fix TypedResponse so that Typescript correctly shows errors for incompatible types in loader and action functions. (#4734)

    Previously, when the return type of a loader or action was explicitly set to TypedResponse<SomeType>,
    Typescript would not show errors when the function 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 object's json property before intersecting with { json: () => Promise<T> }.

  • Optimize parentRouteId lookup in defineConventionalRoutes. (#4800)

  • Fixed a bug in .ts -> .js conversion on Windows by using a relative unix-style path (#4718)

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

@remix-run/architect@1.9.0

Patch Changes

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

@remix-run/cloudflare@1.9.0

Patch Changes

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

@remix-run/cloudflare-pages@1.9.0

Patch Changes

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

@remix-run/cloudflare-workers@1.9.0

Patch Changes

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

@remix-run/deno@1.9.0

Patch Changes

  • Fixed type issues for the request handler context (#4715)
  • Updated dependencies:
    • @remix-run/server-runtime@1.9.0

@remix-run/express@1.9.0

Patch Changes

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

@remix-run/netlify@1.9.0

Patch Changes

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

@remix-run/node@1.9.0

Patch Changes

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

@remix-run/react@1.9.0

Patch Changes

  • Update @remix-run/react to use Router from react-router-dom@6.5.0 (#4731)
  • Allow pass-through props to be passed to the script rendered by ScrollRestoration (#2879)
  • Fixed a problem with <LiveReload> and Firefox infinitely reloading the page. (#4725)

@remix-run/serve@1.9.0

Patch Changes

  • Fix TypedResponse so that Typescript correctly shows errors for incompatible types in loader and action functions. (#4734)

    Previously, when the return type of a loader or action was explicitly set to TypedResponse<SomeType>,
    Typescript would not show errors when the function 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 object's json property before intersecting with { json: () => Promise<T> }.

  • Updated dependencies:

    • @remix-run/express@1.9.0

@remix-run/server-runtime@1.9.0

Patch Changes

  • Fix TypedResponse so that Typescript correctly shows errors for incompatible types in loader and action functions. (#4734)

    Previously, when the return type of a loader or action was explicitly set to TypedResponse<SomeType>,
    Typescript would not show errors when the function 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 object's json property before intersecting with { json: () => Promise<T> }.

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

  • Fixed an issue where a loader's Request object reflected method: "POST" on document submissions (a74e51830)

@remix-run/testing@1.9.0

Patch Changes

  • Updated dependencies:
    • @remix-run/react@1.9.0
    • @remix-run/server-runtime@1.9.0
    • @remix-run/node@1.9.0

@remix-run/vercel@1.9.0

Patch Changes

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

@remix-run/eslint-config@1.9.0

@chaance chaance merged commit 3ed7906 into release-next Dec 16, 2022
@chaance chaance deleted the changeset-release/release-next branch December 16, 2022 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants