chore: Update version for release

[mcansh]

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/cloudflare@1.15.0

Minor Changes

• We have made a few changes to the API for route module meta functions when using the future.v2_meta flag. These changes are only breaking for users who have opted in. (#5746)

  • V2_HtmlMetaDescriptor has been renamed to V2_MetaDescriptor
  • The meta function's arguments have been simplified
    • parentsData has been removed, as each route's loader data is available on the data property of its respective match object

      // before
      export function meta({ parentsData }) {
        return [{ title: parentsData["routes/some-route"].title }];
      }
      // after
      export function meta({ matches }) {
        return [
          {
            title: matches.find((match) => match.id === "routes/some-route")
              .data.title,
          },
        ];
      }

    • The route property on route matches has been removed, as relevant match data is attached directly to the match object

      // before
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.route.id === "root");
      }
      // after
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.id === "root");
      }

  • Added support for generating <script type='application/ld+json' /> and meta-related <link /> tags to document head via the route meta function when using the v2_meta future flag

Patch Changes

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

@remix-run/deno@1.15.0

Minor Changes

• We have made a few changes to the API for route module meta functions when using the future.v2_meta flag. These changes are only breaking for users who have opted in. (#5746)

  • V2_HtmlMetaDescriptor has been renamed to V2_MetaDescriptor
  • The meta function's arguments have been simplified
    • parentsData has been removed, as each route's loader data is available on the data property of its respective match object

      // before
      export function meta({ parentsData }) {
        return [{ title: parentsData["routes/some-route"].title }];
      }
      // after
      export function meta({ matches }) {
        return [
          {
            title: matches.find((match) => match.id === "routes/some-route")
              .data.title,
          },
        ];
      }

    • The route property on route matches has been removed, as relevant match data is attached directly to the match object

      // before
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.route.id === "root");
      }
      // after
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.id === "root");
      }

  • Added support for generating <script type='application/ld+json' /> and meta-related <link /> tags to document head via the route meta function when using the v2_meta future flag

Patch Changes

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

@remix-run/dev@1.15.0

Minor Changes

• Added deprecation warning for v2_normalizeFormMethod (#5863)

• Added a new future.v2_normalizeFormMethod flag to normalize the exposed useNavigation().formMethod as an uppercase HTTP method to align with the previous useTransition behavior as well as the fetch() behavior of normalizing to uppercase HTTP methods. (#5815)

  • When future.v2_normalizeFormMethod === false,
    • useNavigation().formMethod is lowercase
    • useFetcher().formMethod is uppercase
  • When future.v2_normalizeFormMethod === true:
    • useNavigation().formMethod is uppercase
    • useFetcher().formMethod is uppercase

• Added deprecation warning for browserBuildDirectory in remix.config (#5702)

• Added deprecation warning for CatchBoundary in favor of future.v2_errorBoundary (#5718)

• Added experimental support for Vanilla Extract caching, which can be enabled by setting future.unstable_vanillaExtract: { cache: true } in remix.config. This is considered experimental due to the use of a brand new Vanilla Extract compiler under the hood. In order to use this feature, you must be using at least v1.10.0 of @vanilla-extract/css. (#5735)

• Added deprecation warning for serverBuildDirectory in remix.config (#5704)

Patch Changes

• Fixed issue to ensure changes to CSS inserted via @remix-run/css-bundle are picked up during HMR (#5823)
• We now use path.resolve when re-exporting entry.client (#5707)
• Added support for .mjs and .cjs extensions when detecting CSS side-effect imports (#5564)
• Fixed resolution issues for pnpm users installing react-refresh (#5637)
• Added deprecation warning for future.v2_meta (#5878)
• Added optional entry file support for React 17 (#5681)
• Updated dependencies:
  • @remix-run/server-runtime@1.15.0

@remix-run/node@1.15.0

Minor Changes

• We have made a few changes to the API for route module meta functions when using the future.v2_meta flag. These changes are only breaking for users who have opted in. (#5746)

  • V2_HtmlMetaDescriptor has been renamed to V2_MetaDescriptor
  • The meta function's arguments have been simplified
    • parentsData has been removed, as each route's loader data is available on the data property of its respective match object

      // before
      export function meta({ parentsData }) {
        return [{ title: parentsData["routes/some-route"].title }];
      }
      // after
      export function meta({ matches }) {
        return [
          {
            title: matches.find((match) => match.id === "routes/some-route")
              .data.title,
          },
        ];
      }

    • The route property on route matches has been removed, as relevant match data is attached directly to the match object

      // before
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.route.id === "root");
      }
      // after
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.id === "root");
      }

  • Added support for generating <script type='application/ld+json' /> and meta-related <link /> tags to document head via the route meta function when using the v2_meta future flag

Patch Changes

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

@remix-run/react@1.15.0

Minor Changes

• Deprecated fetcher.type and fetcher.submission for Remix v2 (#5691)

• We have made a few changes to the API for route module meta functions when using the future.v2_meta flag. These changes are only breaking for users who have opted in. (#5746)

  • V2_HtmlMetaDescriptor has been renamed to V2_MetaDescriptor
  • The meta function's arguments have been simplified
    • parentsData has been removed, as each route's loader data is available on the data property of its respective match object

      // before
      export function meta({ parentsData }) {
        return [{ title: parentsData["routes/some-route"].title }];
      }
      // after
      export function meta({ matches }) {
        return [
          {
            title: matches.find((match) => match.id === "routes/some-route")
              .data.title,
          },
        ];
      }

    • The route property on route matches has been removed, as relevant match data is attached directly to the match object

      // before
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.route.id === "root");
      }
      // after
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.id === "root");
      }

  • Added support for generating <script type='application/ld+json' /> and meta-related <link /> tags to document head via the route meta function when using the v2_meta future flag

• Added deprecation warning for v2_normalizeFormMethod (#5863)

• Added a new future.v2_normalizeFormMethod flag to normalize the exposed useNavigation().formMethod as an uppercase HTTP method to align with the previous useTransition behavior as well as the fetch() behavior of normalizing to uppercase HTTP methods. (#5815)

  • When future.v2_normalizeFormMethod === false,
    • useNavigation().formMethod is lowercase
    • useFetcher().formMethod is uppercase
  • When future.v2_normalizeFormMethod === true:
    • useNavigation().formMethod is uppercase
    • useFetcher().formMethod is uppercase

• Added deprecation warning for normalizing imagesizes & imagesrcset properties returned from the route links function. Both properties should be in camelCase (imageSizes/ imageSrcSet) to align with their respective JavaScript properties. (#5706)

• Added deprecation warning for CatchBoundary in favor of future.v2_errorBoundary (#5718)

• Added experimental support for Vanilla Extract caching, which can be enabled by setting future.unstable_vanillaExtract: { cache: true } in remix.config. This is considered experimental due to the use of a brand new Vanilla Extract compiler under the hood. In order to use this feature, you must be using at least v1.10.0 of @vanilla-extract/css. (#5735)

Patch Changes

• Bumped React Router dependencies to the latest version. See the release notes for more details. (e14699547)
• Added type deprecations for types now in React Router (#5679)

@remix-run/server-runtime@1.15.0

Minor Changes

• We have made a few changes to the API for route module meta functions when using the future.v2_meta flag. These changes are only breaking for users who have opted in. (#5746)

  • V2_HtmlMetaDescriptor has been renamed to V2_MetaDescriptor
  • The meta function's arguments have been simplified
    • parentsData has been removed, as each route's loader data is available on the data property of its respective match object

      // before
      export function meta({ parentsData }) {
        return [{ title: parentsData["routes/some-route"].title }];
      }
      // after
      export function meta({ matches }) {
        return [
          {
            title: matches.find((match) => match.id === "routes/some-route")
              .data.title,
          },
        ];
      }

    • The route property on route matches has been removed, as relevant match data is attached directly to the match object

      // before
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.route.id === "root");
      }
      // after
      export function meta({ matches }) {
        let rootModule = matches.find((match) => match.id === "root");
      }

  • Added support for generating <script type='application/ld+json' /> and meta-related <link /> tags to document head via the route meta function when using the v2_meta future flag

• Added a new future.v2_normalizeFormMethod flag to normalize the exposed useNavigation().formMethod as an uppercase HTTP method to align with the previous useTransition behavior as well as the fetch() behavior of normalizing to uppercase HTTP methods. (#5815)

  • When future.v2_normalizeFormMethod === false,
    • useNavigation().formMethod is lowercase
    • useFetcher().formMethod is uppercase
  • When future.v2_normalizeFormMethod === true:
    • useNavigation().formMethod is uppercase
    • useFetcher().formMethod is uppercase

• Added deprecation warning for CatchBoundary in favor of future.v2_errorBoundary (#5718)

• Added experimental support for Vanilla Extract caching, which can be enabled by setting future.unstable_vanillaExtract: { cache: true } in remix.config. This is considered experimental due to the use of a brand new Vanilla Extract compiler under the hood. In order to use this feature, you must be using at least v1.10.0 of @vanilla-extract/css. (#5735)

Patch Changes

• Bumped React Router dependencies to the latest version. See the release notes for more details. (e14699547)
• Added type deprecations for types now in React Router (#5679)
• Stopped logging server errors for aborted requests (#5602)
• We now ensure that stack traces are removed from all server side errors in production (#5541)

create-remix@1.15.0

Patch Changes

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

@remix-run/architect@1.15.0

Patch Changes

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

@remix-run/cloudflare-pages@1.15.0

Patch Changes

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

@remix-run/cloudflare-workers@1.15.0

Patch Changes

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

@remix-run/css-bundle@1.15.0

Patch Changes

• Fixed issue to ensure changes to CSS inserted via @remix-run/css-bundle are picked up during HMR (#5823)
• Updated dependencies:
  • @remix-run/dev@1.15.0

@remix-run/eslint-config@1.15.0

Patch Changes

• Updated TypeScript peerDependency to allow for ^5.0.0 (6b6ee66a2)

@remix-run/express@1.15.0

Patch Changes

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

@remix-run/netlify@1.15.0

Patch Changes

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

@remix-run/serve@1.15.0

Patch Changes

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

@remix-run/testing@1.15.0

Patch Changes

• Bumped React Router dependencies to the latest version. See the release notes for more details. (e14699547)
• Updated dependencies:
  • @remix-run/react@1.15.0
  • @remix-run/node@1.15.0

@remix-run/vercel@1.15.0

Patch Changes

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

remix@1.15.0

remix

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

[github-actions]

🤖 Hello there,

We just published version 1.15.0 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!