chore: Update version for release (pre)

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

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

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

@remix-run/deno@1.15.0-pre.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-pre.0

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

Minor Changes

• Add deprecation warnings 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

• show deprecation warning when browserBuildDirectory config is used (#5702)

• Add 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. Note that in order to use this feature, you must be using at least v1.10.0 of @vanilla-extract/css. (#5735)

• show deprecation warning when serverBuildDirectory config is used (#5704)

• add support for tailwind.config.{mjs,ts} (#5850)

Patch Changes

• Ensure changes to CSS inserted via @remix-run/css-bundle are picked up during HMR (#5823)

• use path.resolve when re-exporting entry.client (#5707)

• Add support for .mjs and .cjs extensions when detecting CSS side-effect imports (#5564)

• update entry.client, requestIdleCallback/setTimeout doesn't really do anything more than startTransition. (#5749)

• flat routes perf improvements (#5634)

• resolves an issue when resolving react-refresh for pnpm users (#5637)

• add optional entry file support for React 17 (#5681)

• bumps json5 to resolve a potential security vulneratility (#5799)

  also resolves some other security vulnerabilities in the root package.json used for building/testing remix

• Deprecate CatchBoundary in favor of future.v2_errorBoundary (#5718)

• Updated dependencies:

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

@remix-run/node@1.15.0-pre.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-pre.0

@remix-run/react@1.15.0-pre.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({ parentsData }) {
        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

• Add deprecation warnings 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

• show deprecation warning when imagesizes & imagesizes properties are returned from links function (#5706)

• Add 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. Note that in order to use this feature, you must be using at least v1.10.0 of @vanilla-extract/css. (#5735)

Patch Changes

• Deprecate fetcher.type and fetcher.submission for Remix v2 (#5691)
• Add type deprecations for types now in React Router (#5679)
• Deprecate CatchBoundary in favor of future.v2_errorBoundary (#5718)
• Update to react-router-dom@6.10.0-pre.0 and @remix-run/router@1.5.0-pre.0 (#5866)

@remix-run/server-runtime@1.15.0-pre.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({ parentsData }) {
        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

• Add 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. Note that in order to use this feature, you must be using at least v1.10.0 of @vanilla-extract/css. (#5735)

Patch Changes

• Add type deprecations for types now in React Router (#5679)
• Don't log server errors for aborted requests as that is an expected flow (#5602)
• Deprecate CatchBoundary in favor of future.v2_errorBoundary (#5718)
• Ensure stack traces are removed from all server side errors in production (#5541)
• Update to react-router-dom@6.10.0-pre.0 and @remix-run/router@1.5.0-pre.0 (#5866)

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

Minor Changes

• 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

Patch Changes

• Update to react-router-dom@6.10.0-pre.0 and @remix-run/router@1.5.0-pre.0 (#5866)
• Updated dependencies:
  • @remix-run/react@1.15.0-pre.0
  • @remix-run/node@1.15.0-pre.0

create-remix@1.15.0-pre.0

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

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

@remix-run/css-bundle@1.15.0-pre.0

Patch Changes

• Ensure changes to CSS inserted via @remix-run/css-bundle are picked up during HMR (#5823)
• Updated dependencies:
  • @remix-run/dev@1.15.0-pre.0

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

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

• Updated dependencies:
  • @remix-run/express@1.15.0-pre.0

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

Patch Changes

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

remix@1.15.0-pre.0

remix

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

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

[mcansh]

incorrect code snippets for the second bullet

// before
- export function meta({ parentsData }) {
+ 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");
}

[mcansh]

thanks @brophdawg11, changelogs are the one part i'm not up to par on for changesets haha

[github-actions]

🤖 Hello there,

We just published version 1.15.0-pre.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!

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