Skip to content

chore(deps): bump the remix group with 6 updates - #522

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot-npm_and_yarn-remix-b9e3d07153
Closed

chore(deps): bump the remix group with 6 updates#522
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot-npm_and_yarn-remix-b9e3d07153

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 18, 2023 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the remix group with 6 updates:

Package From To
@remix-run/express 1.18.1 2.0.0
@remix-run/node 1.18.1 2.0.0
@remix-run/react 1.18.1 2.0.0
@remix-run/server-runtime 1.18.1 2.0.0
@remix-run/dev 1.18.1 2.0.0
@remix-run/eslint-config 1.18.1 2.0.0

Updates @remix-run/express from 1.18.1 to 2.0.0

Release notes

Sourced from @​remix-run/express's releases.

v2.0.0

Remix v2

We're so excited to release Remix v2 to you and we really hope this upgrade is one of the smoothest framework upgrades you've ever experienced! That was our primary goal with v2 - something we aimed to achieve through a heavy use of deprecation warnings and Future Flags in Remix v1.

If you are on the latest 1.x version and you've enabled all future flags and addressed all console warnings, then our hope is that you are 90% of the way to being upgraded for v2. There are always going to be a few things that we can't put behind a flag (like breaking type changes) or come up at the very last moment and don't have time to add as a warning or flag in 1.x.

If you're not yet on the latest 1.x version we'd recommend first upgrading to that and resolving any flag/console warnings:

> npx upgrade-remix 1.19.3

Breaking Changes

Below is a very concise list of the breaking changes in v2.

  • For the most thorough discussion of breaking changes, please read the Upgrading to v2 guide. This document provides a comprehensive walkthrough of the breaking changes that come along with v2 - and instructions on how to adapt your application to handle them
  • For additional details, you can refer to the Changes by Package section below

Upgraded Dependency Requirements

Remix v2 has upgraded it's minimum version support for React and Node and now officially supports:

Removed Future Flags

The following future flags were removed and their behavior is now the default - you can remove all of these from your remix.config.js file.

  • v2_dev - New dev server with HMR+HDR (#7002)
    • If you had configurations in future.v2_dev instead of just the boolean value (i.e., future.v2_dev.port), you can lift them into a root dev object in your remix.config.js
  • v2_errorBoundary - Removed CatchBoundary in favor of a singular ErrorBoundary (#6906)
  • v2_headers - Altered the logic for headers in nested route scenarios (#6979)
  • v2_meta - Altered the return format of meta() (#6958)
  • v2_normalizeFormMethod - Normalize formMethod APIs to uppercase (#6875)
  • v2_routeConvention - Routes use a flat route convention by default now (#6969)

Breaking Changes/API Removals

With deprecation warnings

The following lists other breaking changes/API removals which had deprecation warnings in Remix v1. If you're on the latest 1.19.3 release without any console warnings, then you're probably good to go on all of these!

... (truncated)

Changelog

Sourced from @​remix-run/express's changelog.

2.0.0

Major Changes

  • Require Node >=18.0.0 (#6939)

  • For preparation of using Node's built in fetch implementation, installing the fetch globals is now a responsibility of the app server (#7009)

    • If you are using remix-serve, nothing is required

    • If you are using your own app server, you will need to install the globals yourself

      import { installGlobals } from "@remix-run/node";
installGlobals();

  • source-map-support is now a responsibility of the app server (#7009)

    • If you are using remix-serve, nothing is required

    • If you are using your own app server, you will need to install source-map-support yourself.

      npm i source-map-support
      import sourceMapSupport from "source-map-support";
sourceMapSupport.install();

Patch Changes

  • Switch to headers.entries() instead of non-spec-compliant headers.raw() in sendRemixResponse (#7150)
  • Remove references to fetch polyfills in node and arc adapters (#7230)
  • Updated dependencies:
    • @remix-run/node@2.0.0
    • @remix-run/web-fetch@4.4.0
    • @remix-run/web-file@3.1.0
    • @remix-run/web-stream@1.1.0

1.19.3

Patch Changes

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

1.19.2

Patch Changes

... (truncated)

Commits

Updates @remix-run/node from 1.18.1 to 2.0.0

Release notes

Sourced from @​remix-run/node's releases.

v2.0.0

Remix v2

We're so excited to release Remix v2 to you and we really hope this upgrade is one of the smoothest framework upgrades you've ever experienced! That was our primary goal with v2 - something we aimed to achieve through a heavy use of deprecation warnings and Future Flags in Remix v1.

If you are on the latest 1.x version and you've enabled all future flags and addressed all console warnings, then our hope is that you are 90% of the way to being upgraded for v2. There are always going to be a few things that we can't put behind a flag (like breaking type changes) or come up at the very last moment and don't have time to add as a warning or flag in 1.x.

If you're not yet on the latest 1.x version we'd recommend first upgrading to that and resolving any flag/console warnings:

> npx upgrade-remix 1.19.3

Breaking Changes

Below is a very concise list of the breaking changes in v2.

  • For the most thorough discussion of breaking changes, please read the Upgrading to v2 guide. This document provides a comprehensive walkthrough of the breaking changes that come along with v2 - and instructions on how to adapt your application to handle them
  • For additional details, you can refer to the Changes by Package section below

Upgraded Dependency Requirements

Remix v2 has upgraded it's minimum version support for React and Node and now officially supports:

Removed Future Flags

The following future flags were removed and their behavior is now the default - you can remove all of these from your remix.config.js file.

  • v2_dev - New dev server with HMR+HDR (#7002)
    • If you had configurations in future.v2_dev instead of just the boolean value (i.e., future.v2_dev.port), you can lift them into a root dev object in your remix.config.js
  • v2_errorBoundary - Removed CatchBoundary in favor of a singular ErrorBoundary (#6906)
  • v2_headers - Altered the logic for headers in nested route scenarios (#6979)
  • v2_meta - Altered the return format of meta() (#6958)
  • v2_normalizeFormMethod - Normalize formMethod APIs to uppercase (#6875)
  • v2_routeConvention - Routes use a flat route convention by default now (#6969)

Breaking Changes/API Removals

With deprecation warnings

The following lists other breaking changes/API removals which had deprecation warnings in Remix v1. If you're on the latest 1.19.3 release without any console warnings, then you're probably good to go on all of these!

... (truncated)

Changelog

Sourced from @​remix-run/node's changelog.

2.0.0

Major Changes

  • Require Node >=18.0.0 (#6939)

  • Stop exporting the fetch API in favor of using the version in the global scope - which can be polyfilled via installGlobals (#7293)

  • Removed/adjusted types to prefer unknown over any and to align with underlying React Router types (#7319, #7354):

    • Renamed the useMatches() return type from RouteMatch to UIMatch
    • Renamed LoaderArgs/ActionArgs to LoaderFunctionArgs/ActionFunctionArgs
    • AppData changed from any to unknown
    • Location["state"] (useLocation.state) changed from any to unknown
    • UIMatch["data"] (useMatches()[i].data) changed from any to unknown
    • UIMatch["handle"] (useMatches()[i].handle) changed from { [k: string]: any } to unknown
    • Fetcher["data"] (useFetcher().data) changed from any to unknown
    • MetaMatch.handle (used in meta()) changed from any to unknown
    • AppData/RouteHandle are no longer exported as they are just aliases for unknown

  • The route meta API now defaults to the new "V2 Meta" API (#6958)

  • For preparation of using Node's built in fetch implementation, installing the fetch globals is now a responsibility of the app server (#7009)

    • If you are using remix-serve, nothing is required

    • If you are using your own app server, you will need to install the globals yourself

      import { installGlobals } from "@remix-run/node";
installGlobals();

  • source-map-support is now a responsibility of the app server (#7009)

    • If you are using remix-serve, nothing is required

    • If you are using your own app server, you will need to install source-map-support yourself.

      npm i source-map-support
      import sourceMapSupport from "source-map-support";
sourceMapSupport.install();

  • Removed support for "magic exports" from the remix package. This package can be removed from your package.json and you should update all imports to use the source @remix-run/* packages: (#6895)

    - import type { ActionArgs } from "remix";
- import { json, useLoaderData } from "remix";
+ import type { ActionArgs } from "@remix-run/node";
+ import { json } from "@remix-run/node";

... (truncated)

Commits

Updates @remix-run/react from 1.18.1 to 2.0.0

Release notes

Sourced from @​remix-run/react's releases.

v2.0.0

Remix v2

We're so excited to release Remix v2 to you and we really hope this upgrade is one of the smoothest framework upgrades you've ever experienced! That was our primary goal with v2 - something we aimed to achieve through a heavy use of deprecation warnings and Future Flags in Remix v1.

If you are on the latest 1.x version and you've enabled all future flags and addressed all console warnings, then our hope is that you are 90% of the way to being upgraded for v2. There are always going to be a few things that we can't put behind a flag (like breaking type changes) or come up at the very last moment and don't have time to add as a warning or flag in 1.x.

If you're not yet on the latest 1.x version we'd recommend first upgrading to that and resolving any flag/console warnings:

> npx upgrade-remix 1.19.3

Breaking Changes

Below is a very concise list of the breaking changes in v2.

  • For the most thorough discussion of breaking changes, please read the Upgrading to v2 guide. This document provides a comprehensive walkthrough of the breaking changes that come along with v2 - and instructions on how to adapt your application to handle them
  • For additional details, you can refer to the Changes by Package section below

Upgraded Dependency Requirements

Remix v2 has upgraded it's minimum version support for React and Node and now officially supports:

Removed Future Flags

The following future flags were removed and their behavior is now the default - you can remove all of these from your remix.config.js file.

  • v2_dev - New dev server with HMR+HDR (#7002)
    • If you had configurations in future.v2_dev instead of just the boolean value (i.e., future.v2_dev.port), you can lift them into a root dev object in your remix.config.js
  • v2_errorBoundary - Removed CatchBoundary in favor of a singular ErrorBoundary (#6906)
  • v2_headers - Altered the logic for headers in nested route scenarios (#6979)
  • v2_meta - Altered the return format of meta() (#6958)
  • v2_normalizeFormMethod - Normalize formMethod APIs to uppercase (#6875)
  • v2_routeConvention - Routes use a flat route convention by default now (#6969)

Breaking Changes/API Removals

With deprecation warnings

The following lists other breaking changes/API removals which had deprecation warnings in Remix v1. If you're on the latest 1.19.3 release without any console warnings, then you're probably good to go on all of these!

... (truncated)

Changelog

Sourced from @​remix-run/react's changelog.

2.0.0

Major Changes

  • Drop React 17 support (#7121)

  • Require Node >=18.0.0 (#6939)

  • Remove unstable_shouldReload, which has been replaced by shouldRevalidate (#6865)

  • The route meta API now defaults to the new "V2 Meta" API (#6958)

  • Promote the future.v2_dev flag in remix.config.js to a root level dev config (#7002)

  • Remove v2_errorBoundary flag and CatchBoundary implementation (#6906)

  • Remove back-compat layer for useFetcher/useFetchers, which includes a few small breaking changes (#6874)

    • fetcher.type has been removed since it can be derived from other available information
    • "Submission" fields have been flattened from fetcher.submission down onto the root fetcher object, and prefixed with form in some cases (fetcher.submission.action => fetcher.formAction)
    • <fetcher.Form method="get"> is now more accurately categorized as state:"loading" instead of state:"submitting" to better align with the underlying GET request

  • Remove v2_normalizeFormMethod future flag - all formMethod values will be normalized in v2 (#6875)

  • Remove deprecated useTransition hook in favor of useNavigation - useNavigation is almost identical with a few exceptions: (#6870)

    • useTransition.type has been removed since it can be derived from other available information
    • "Submission" fields have been flattened from useTransition().submission down onto the root useNavigation() object
    • <Form method="get"> is now more accurately categorized as state:"loading" instead of state:"submitting" to better align with the underlying GET navigation

  • Remove v2_routeConvention flag - the flat route file convention is now standard. (#6969)

  • Remove v2_headers flag - it is now the default behavior to use the deepest headers function in the route tree. (#6979)

  • Removed/adjusted types to prefer unknown over any and to align with underlying React Router types (#7319, #7354):

    • Renamed the useMatches() return type from RouteMatch to UIMatch
    • Renamed LoaderArgs/ActionArgs to LoaderFunctionArgs/ActionFunctionArgs
    • AppData changed from any to unknown
    • Location["state"] (useLocation.state) changed from any to unknown
    • UIMatch["data"] (useMatches()[i].data) changed from any to unknown
    • UIMatch["handle"] (useMatches()[i].handle) changed from { [k: string]: any } to unknown
    • Fetcher["data"] (useFetcher().data) changed from any to unknown
    • MetaMatch.handle (used in meta()) changed from any to unknown
    • AppData/RouteHandle are no longer exported as they are just aliases for unknown

  • Remove imagesizes & imagesrcset properties from HtmlLinkDescriptor, LinkDescriptor & PrefetchPageDescriptor types (#6936)

  • Remove deprecated REMIX_DEV_SERVER_WS_PORT env var (#6965)

    • use remix dev's '--port/port option instead

  • Removed support for "magic exports" from the remix package. This package can be removed from your package.json and you should update all imports to use the source @remix-run/* packages: (#6895)

    - import type { ActionArgs } from "remix";
- import { json, useLoaderData } from "remix";
+ import type { ActionArgs } from "@remix-run/node";
+ import { json } from "@remix-run/node";
+ import { useLoaderData } from "@remix-run/react";

Minor Changes

  • Export the Navigation type returned from useNavigation (#7136)
  • Update Remix to use React Router route.lazy for module loading (#7133)

... (truncated)

Commits

Updates @remix-run/server-runtime from 1.18.1 to 2.0.0

Release notes

Sourced from @​remix-run/server-runtime's releases.

v2.0.0

Remix v2

We're so excited to release Remix v2 to you and we really hope this upgrade is one of the smoothest framework upgrades you've ever experienced! That was our primary goal with v2 - something we aimed to achieve through a heavy use of deprecation warnings and Future Flags in Remix v1.

If you are on the latest 1.x version and you've enabled all future flags and addressed all console warnings, then our hope is that you are 90% of the way to being upgraded for v2. There are always going to be a few things that we can't put behind a flag (like breaking type changes) or come up at the very last moment and don't have time to add as a warning or flag in 1.x.

If you're not yet on the latest 1.x version we'd recommend first upgrading to that and resolving any flag/console warnings:

> npx upgrade-remix 1.19.3

Breaking Changes

Below is a very concise list of the breaking changes in v2.

  • For the most thorough discussion of breaking changes, please read the Upgrading to v2 guide. This document provides a comprehensive walkthrough of the breaking changes that come along with v2 - and instructions on how to adapt your application to handle them
  • For additional details, you can refer to the Changes by Package section below

Upgraded Dependency Requirements

Remix v2 has upgraded it's minimum version support for React and Node and now officially supports:

Removed Future Flags

The following future flags were removed and their behavior is now the default - you can remove all of these from your remix.config.js file.

  • v2_dev - New dev server with HMR+HDR (#7002)
    • If you had configurations in future.v2_dev instead of just the boolean value (i.e., future.v2_dev.port), you can lift them into a root dev object in your remix.config.js
  • v2_errorBoundary - Removed CatchBoundary in favor of a singular ErrorBoundary (#6906)
  • v2_headers - Altered the logic for headers in nested route scenarios (#6979)
  • v2_meta - Altered the return format of meta() (#6958)
  • v2_normalizeFormMethod - Normalize formMethod APIs to uppercase (#6875)
  • v2_routeConvention - Routes use a flat route convention by default now (#6969)

Breaking Changes/API Removals

With deprecation warnings

The following lists other breaking changes/API removals which had deprecation warnings in Remix v1. If you're on the latest 1.19.3 release without any console warnings, then you're probably good to go on all of these!

... (truncated)

Changelog

Sourced from @​remix-run/server-runtime's changelog.

2.0.0

Major Changes

  • Require Node >=18.0.0 (#6939)

  • The route meta API now defaults to the new "V2 Meta" API (#6958)

  • Promote the future.v2_dev flag in remix.config.js to a root level dev config (#7002)

  • Remove v2_errorBoundary flag and CatchBoundary implementation (#6906)

  • Remove v2_normalizeFormMethod future flag - all formMethod values will be normalized in v2 (#6875)

  • Remove v2_routeConvention flag - the flat route file convention is now standard (#6969)

  • Remove v2_headers flag - it is now the default behavior to use the deepest headers function in the route tree (#6979)

  • Remove imagesizes & imagesrcset properties from HtmlLinkDescriptor, LinkDescriptor & PrefetchPageDescriptor types (#6936)

  • Removed/adjusted types to prefer unknown over any and to align with underlying React Router types (#7319, #7354):

    • Renamed the useMatches() return type from RouteMatch to UIMatch
    • Renamed LoaderArgs/ActionArgs to LoaderFunctionArgs/ActionFunctionArgs
    • AppData changed from any to unknown
    • Location["state"] (useLocation.state) changed from any to unknown
    • UIMatch["data"] (useMatches()[i].data) changed from any to unknown
    • UIMatch["handle"] (useMatches()[i].handle) changed from { [k: string]: any } to unknown
    • Fetcher["data"] (useFetcher().data) changed from any to unknown
    • MetaMatch.handle (used in meta()) changed from any to unknown
    • AppData/RouteHandle are no longer exported as they are just aliases for unknown

  • Remove deprecated REMIX_DEV_HTTP_ORIGIN env var - use REMIX_DEV_ORIGIN instead (#6963)

  • Removed support for "magic exports" from the remix package. This package can be removed from your package.json and you should update all imports to use the source @remix-run/* packages: (#6895)

    - import type { ActionArgs } from "remix";
- import { json, useLoaderData } from "remix";
+ import type { ActionArgs } from "@remix-run/node";
+ import { json } from "@remix-run/node";
+ import { useLoaderData } from "@remix-run/react";

Minor Changes

  • Update Remix to use React Router route.lazy for module loading (#7133)
  • Detect built mode via build.mode (#6964)
    • Prevents mode mismatch between built Remix server entry and user-land server
    • Additionally, all runtimes (including non-Node runtimes) can use build.mode to determine if HMR should be performed.
  • Re-export the new redirectDocument method from React Router (#7040, #6842) (#7040)

Patch Changes

  • Export proper ErrorResponse type for usage alongside isRouteErrorResponse (#7244)
  • Fix destroySession for sessions using a maxAge cookie (#7252)
    • The data in the cookie was always properly destroyed but when using maxAge, the cookie itself wasn't deleted because Max-Age takes precedence over Expires in the cookie spec
  • Ensure maxAge/expires options passed to commitSession take precedence over the original cookie.expires value (#6598, #7374)
  • Fix handleError method to correctly receive ErrorResponse instances on ?_data and resource route requests (#7211)
    • It now receives the ErrorResponse instance the same way a document request would

... (truncated)

Commits
  • e547efd chore: Update version for release (#7430)
  • fb82201 chore: Update version for release (pre) (#7428)
  • 892dce9 chore: Update version for release (pre) (#7407)
  • bef63b7 Update to stable releases of web-std-io and react-router (#7406)
  • 99cf6ff chore: Update version for release (pre) (#7401)
  • 08d492f Add back in required AppLoadContext to DataFunctionArgs (#7403)
  • 1071209 chore: Update version for release (pre) (#7380)
  • 4f133c4 fix(remix-server-runtime): make DataFunctionArgs a type alias (#7362)
  • 3214f76 chore: Update version for release (pre) (#7359)
  • fe948cc Revert AppLoadContext back to an interface for module augmentation su… (#7360)
  • Additional commits viewable in compare view

Updates @remix-run/dev from 1.18.1 to 2.0.0

Release notes

Sourced from @​remix-run/dev's releases.

v2.0.0

Remix v2

We're so excited to release Remix v2 to you and we really hope this upgrade is one of the smoothest framework upgrades you've ever experienced! That was our primary goal with v2 - something we aimed to achieve through a heavy use of deprecation warnings and Future Flags in Remix v1.

If you are on the latest 1.x version and you've enabled all future flags and addressed all console warnings, then our hope is that you are 90% of the way to being upgraded for v2. There are always going to be a few things that we can't put behind a flag (like breaking type changes) or come up at the very last moment and don't have time to add as a warning or flag in 1.x.

If you're not yet on the latest 1.x version we'd recommend first upgrading to that and resolving any flag/console warnings:

> npx upgrade-remix 1.19.3

Breaking Changes

Below is a very concise list of the breaking changes in v2.

  • For the most thorough discussion of breaking changes, please read the Upgrading to v2 guide. This document provides a comprehensive walkthrough of the breaking changes that come along with v2 - and instructions on how to adapt your application to handle them
  • For additional details, you can refer to the Changes by Package section below

Upgraded Dependency Requirements

Remix v2 has upgraded it's minimum version support for React and Node and now officially supports:

Removed Future Flags

The following future flags were removed and their behavior is now the default - you can remove all of these from your remix.config.js file.

  • v2_dev - New dev server with HMR+HDR (#7002)
    • If you had configurations in future.v2_dev instead of just the boolean value (i.e., future.v2_dev.port), you can lift them into a root dev object in your remix.config.js
  • v2_errorBoundary - Removed CatchBoundary in favor of a singular ErrorBoundary (#6906)
  • v2_headers - Altered the logic for headers in nested route scenarios (#6979)
  • v2_meta - Altered the return format of meta() (#6958)
  • v2_normalizeFormMethod - Normalize formMethod APIs to uppercase (#6875)
  • v2_routeConvention - Routes use a flat route convention by default now (#6969)

Breaking Changes/API Removals

With deprecation warnings

The following lists other breaking changes/API removals which had deprecation warnings in Remix v1. If you're on the latest 1.19.3 release without any console warnings, then you're probably good to go on all of these!

... (truncated)

Changelog

Sourced from @​remix-run/dev's changelog.

2.0.0

Major Changes

  • The create-remix CLI has been rewritten to feature a cleaner interface, Git repo initialization and optional remix.init script execution. The interactive template prompt and official Remix stack/template shorthands have also been removed so that community/third-party templates are now on a more equal footing. (#6887)

    • The code for create-remix has been moved out of the Remix CLI since it's not intended for use within an existing Remix application
    • This means that the remix create command is no longer available.

  • Enable built-in PostCSS and Tailwind support by default. (#6909)

    • These tools are now automatically used within the Remix compiler if PostCSS and/or Tailwind configuration files are present in your project.
    • If you have a custom PostCSS and/or Tailwind setup outside of Remix, you can disable these features in your remix.config.js via the postcss:false and/or tailwind:false flags

  • Drop React 17 support (#7121)

  • Require Node >=18.0.0 (#6939)

  • Compile server build to Node 18 (#7292)

    • This allows features like top-level await to be used within a Remix app

  • Remove default Node.js polyfills - you must now opt-into polyfills via the serverNodeBuiltinsPolyfill and browserNodeBuiltinsPolyfill configs (#7269)

  • Remove v2_errorBoundary flag and CatchBoundary implementation (#6906)

  • Remove v2_normalizeFormMethod future flag - all formMethod values will be normalized in v2 (#6875)

  • Remove v2_routeConvention flag - the flat route file convention is now standard (#6969)

  • Remove v2_headers flag - it is now the default behavior to use the deepest headers function in the route tree (#6979)

  • The route meta API now defaults to the new "V2 Meta" API (#6958)

  • Default to serverModuleFormat: "esm" and update remix-serve to use dynamic import to support ESM and CJS build outputs (#6949)

  • Remove serverBuildTarget config option (#6896)

  • Remove deprecated REMIX_DEV_HTTP_ORIGIN env var - use REMIX_DEV_ORIGIN instead (#6963)

  • Remove devServerBroadcastDelay config option (#7063)

  • Remove deprecated devServerPort option - use --port / dev.port instead (#7078)

  • Remove deprecated REMIX_DEV_SERVER_WS_PORT env var - use remix dev's '--port / port option instead (#6965)

  • Stop passing isTypeScript to remix.init script (#7099)

  • Remove replace-remix-magic-imports codemod (#6899)

  • Remove deprecated --no-restart/restart cli args/flags - use --manual/manual instead (#6962)

  • Remove deprecated --scheme/scheme and --host/host cli args/flags - use REMIX_DEV_ORIGIN instead (#6962)

  • Promote the future.v2_dev flag in remix.config.js to a root level Description has been truncated

@dependabot
chore(deps): bump the remix group with 6 updates
00fc5e5 
Bumps the remix group with 6 updates:

| Package | From | To |
| --- | --- | --- |
| [@remix-run/express](https://github.com/remix-run/remix/tree/HEAD/packages/remix-express) | `1.18.1` | `2.0.0` |
| [@remix-run/node](https://github.com/remix-run/remix/tree/HEAD/packages/remix-node) | `1.18.1` | `2.0.0` |
| [@remix-run/react](https://github.com/remix-run/remix/tree/HEAD/packages/remix-react) | `1.18.1` | `2.0.0` |
| [@remix-run/server-runtime](https://github.com/remix-run/remix/tree/HEAD/packages/remix-server-runtime) | `1.18.1` | `2.0.0` |
| [@remix-run/dev](https://github.com/remix-run/remix/tree/HEAD/packages/remix-dev) | `1.18.1` | `2.0.0` |
| [@remix-run/eslint-config](https://github.com/remix-run/remix/tree/HEAD/packages/remix-eslint-config) | `1.18.1` | `2.0.0` |


Updates `@remix-run/express` from 1.18.1 to 2.0.0
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-express/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/express@2.0.0/packages/remix-express)

Updates `@remix-run/node` from 1.18.1 to 2.0.0
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-node/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/node@2.0.0/packages/remix-node)

Updates `@remix-run/react` from 1.18.1 to 2.0.0
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-react/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/react@2.0.0/packages/remix-react)

Updates `@remix-run/server-runtime` from 1.18.1 to 2.0.0
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-server-runtime/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/server-runtime@2.0.0/packages/remix-server-runtime)

Updates `@remix-run/dev` from 1.18.1 to 2.0.0
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-dev/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/dev@2.0.0/packages/remix-dev)

Updates `@remix-run/eslint-config` from 1.18.1 to 2.0.0
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-eslint-config/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/eslint-config@2.0.0/packages/remix-eslint-config)

---
updated-dependencies:
- dependency-name: "@remix-run/express"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: remix
- dependency-name: "@remix-run/node"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: remix
- dependency-name: "@remix-run/react"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: remix
- dependency-name: "@remix-run/server-runtime"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: remix
- dependency-name: "@remix-run/dev"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: remix
- dependency-name: "@remix-run/eslint-config"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: remix
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 18, 2023
@dependabot @github

dependabot Bot commented on behalf of github Sep 25, 2023

Copy link
Copy Markdown
Contributor Author

Superseded by #531.

@dependabot dependabot Bot closed this Sep 25, 2023
@dependabot
dependabot Bot deleted the dependabot-npm_and_yarn-remix-b9e3d07153 branch September 25, 2023 03:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants