From 8b09abb25b16a754ad71c2232d5dcfc616fcf61c Mon Sep 17 00:00:00 2001 From: Chance Strickland Date: Fri, 16 Dec 2022 12:20:15 -0800 Subject: [PATCH] update changelogs --- packages/remix-dev/CHANGELOG.md | 22 ---------------- packages/remix-eslint-config/CHANGELOG.md | 2 ++ packages/remix-serve/CHANGELOG.md | 20 --------------- packages/remix-server-runtime/CHANGELOG.md | 20 --------------- packages/remix/CHANGELOG.md | 29 ---------------------- 5 files changed, 2 insertions(+), 91 deletions(-) diff --git a/packages/remix-dev/CHANGELOG.md b/packages/remix-dev/CHANGELOG.md index 7d06118feb4..23db12d3e75 100644 --- a/packages/remix-dev/CHANGELOG.md +++ b/packages/remix-dev/CHANGELOG.md @@ -7,28 +7,6 @@ - Allow defining multiple routes for the same route module file ([#3970](https://github.com/remix-run/remix/pull/3970)) - Added support and conventions for optional route segments ([#4706](https://github.com/remix-run/remix/pull/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](https://github.com/remix-run/remix/pull/4754)) diff --git a/packages/remix-eslint-config/CHANGELOG.md b/packages/remix-eslint-config/CHANGELOG.md index 5eb12171ccd..ea5f93ddcc8 100644 --- a/packages/remix-eslint-config/CHANGELOG.md +++ b/packages/remix-eslint-config/CHANGELOG.md @@ -2,6 +2,8 @@ ## 1.9.0 +No significant changes to this package were made in this release. [See the releases page on GitHub](https://github.com/remix-run/remix/releases/tag/remix%401.9.0) for an overview of all changes in v1.9.0. + ## 1.8.2 No significant changes to this package were made in this release. [See the releases page on GitHub](https://github.com/remix-run/remix/releases/tag/remix%401.8.2) for an overview of all changes in v1.8.2. diff --git a/packages/remix-serve/CHANGELOG.md b/packages/remix-serve/CHANGELOG.md index e39f2002298..0704790764a 100644 --- a/packages/remix-serve/CHANGELOG.md +++ b/packages/remix-serve/CHANGELOG.md @@ -5,26 +5,6 @@ ### Patch Changes - Fix `TypedResponse` so that Typescript correctly shows errors for incompatible types in `loader` and `action` functions. ([#4734](https://github.com/remix-run/remix/pull/4734)) - - Previously, when the return type of a `loader` or `action` was explicitly set to `TypedResponse`, - Typescript would not show errors when the function returned an incompatible type. - - For example: - - ```ts - export const action = async ( - args: ActionArgs - ): Promise> => { - 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`, but because `TypedReponse` was previously just `Response & { json: () => Promise }` and `Response` already defines `{ json: () => Promise }`, type erasure caused `Promise` to be used for `42`. - - To fix this, we explicitly omit the `Response` object's `json` property before intersecting with `{ json: () => Promise }`. - - Updated dependencies: - `@remix-run/express@1.9.0` diff --git a/packages/remix-server-runtime/CHANGELOG.md b/packages/remix-server-runtime/CHANGELOG.md index 444cd02adf2..b1343cc1e9c 100644 --- a/packages/remix-server-runtime/CHANGELOG.md +++ b/packages/remix-server-runtime/CHANGELOG.md @@ -5,26 +5,6 @@ ### Patch Changes - Fix `TypedResponse` so that Typescript correctly shows errors for incompatible types in `loader` and `action` functions. ([#4734](https://github.com/remix-run/remix/pull/4734)) - - Previously, when the return type of a `loader` or `action` was explicitly set to `TypedResponse`, - Typescript would not show errors when the function returned an incompatible type. - - For example: - - ```ts - export const action = async ( - args: ActionArgs - ): Promise> => { - 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`, but because `TypedReponse` was previously just `Response & { json: () => Promise }` and `Response` already defines `{ json: () => Promise }`, type erasure caused `Promise` to be used for `42`. - - To fix this, we explicitly omit the `Response` object's `json` property before intersecting with `{ json: () => Promise }`. - - Fix error boundary tracking for multiple errors bubbling to the same boundary ([#4829](https://github.com/remix-run/remix/pull/4829)) - Fixed an issue where a loader's `Request` object reflected `method: "POST"` on document submissions ([`a74e51830`](https://github.com/remix-run/remix/commit/a74e51830ec7ecb3ad30e45013270ebf71d7b425)) diff --git a/packages/remix/CHANGELOG.md b/packages/remix/CHANGELOG.md index 9ddba53e353..8ec9b176ee2 100644 --- a/packages/remix/CHANGELOG.md +++ b/packages/remix/CHANGELOG.md @@ -1,32 +1,3 @@ # `remix` -## 1.9.0 - -### Patch Changes - -- The Remix compiler now supports new Typescript 4.9 syntax (like the `satisfies` keyword) ([#4754](https://github.com/remix-run/remix/pull/4754)) -- Fix `TypedResponse` so that Typescript correctly shows errors for incompatible types in `loader` and `action` functions. ([#4734](https://github.com/remix-run/remix/pull/4734)) - - Previously, when the return type of a `loader` or `action` was explicitly set to `TypedResponse`, - Typescript would not show errors when the function returned an incompatible type. - - For example: - - ```ts - export const action = async ( - args: ActionArgs - ): Promise> => { - 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`, but because `TypedReponse` was previously just `Response & { json: () => Promise }` and `Response` already defines `{ json: () => Promise }`, type erasure caused `Promise` to be used for `42`. - - To fix this, we explicitly omit the `Response` object's `json` property before intersecting with `{ json: () => Promise }`. - -- Optimize `parentRouteId` lookup in `defineConventionalRoutes`. ([#4800](https://github.com/remix-run/remix/pull/4800)) -- Fixed a bug in `.ts` -> `.js` conversion on Windows by using a relative unix-style path ([#4718](https://github.com/remix-run/remix/pull/4718)) - See the `CHANGELOG.md` in individual Remix packages for all changes.