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.

Sign up for GitHub

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

Jump to bottom

Bump the remix group with 5 updates #2100

Closed
wants to merge 1 commit into from
Closed

Bump the remix group with 5 updates #2100

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 14, 2023 •
edited
Loading

Bumps the remix group with 5 updates:

Package From To
@remix-run/node 1.19.3 2.4.0
@remix-run/react 1.19.3 2.4.0
@remix-run/serve 1.19.3 2.4.0
@remix-run/dev 1.19.3 2.4.0
@remix-run/eslint-config 1.19.3 2.4.0

Updates @remix-run/node from 1.19.3 to 2.4.0

Release notes

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

v2.4.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v240

v2.3.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v231

v2.3.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v230

v2.2.0

Minor Changes

Vite!

Remix 2.2.0 adds unstable support for Vite for Node-based apps! See our announcement blog post and the Future > Vite page in the Remix docs for more details. (#7590)

You can try it out today with two new (unstable) templates:

# minimal server
npx create-remix@latest --template remix-run/remix/templates/unstable-vite

custom server (Express example)


npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express

New APIs in @remix-run/dev

  • unstable_vitePlugin: The new Remix Vite plugin
  • unstable_createViteServer: Creates a Vite server in middleware mode for interop with custom servers
  • unstable_loadViteServerBuild: Allows your custom server to delegate SSR requests to Vite during development

Changed APIs

  • createRequestHandler: Now also allows the build argument to be a function that will be used to dynamically load new builds for each request during development

Other Runtimes

  • Deno support is untested, but should work through Deno's Node/npm interop
  • CloudFlare support is not yet available

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors. (#10960)

  • You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
  • Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
  • Form and useSumbit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
    • <Form method="post" navigate={false} fetcherKey="my-key">
    • submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })

... (truncated)

Changelog

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

2.4.0

Minor Changes

  • Deprecate DataFunctionArgs in favor of LoaderFunctionArgs/ActionFunctionArgs. This is aimed at keeping the types aligned across server/client loaders/actions now that clientLoader/clientActon functions have serverLoader/serverAction parameters which differentiate ClientLoaderFunctionArgs/ClientActionFunctionArgs. (#8173)

Patch Changes

  • Update to @remix-run/web-fetch@4.4.2 (#8231)
  • Updated dependencies:
    • @remix-run/server-runtime@2.4.0

2.3.1

Patch Changes

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

2.3.0

Patch Changes

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

2.2.0

Patch Changes

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

2.1.0

Patch Changes

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

2.0.1

Patch Changes

  • Switch from crypto.randomBytes to crypto.webcrypto.getRandomValues for file session storage ID generation (#7203)
  • Use native Blob class instead of polyfill (#7217)
  • Updated dependencies:

... (truncated)

Commits

Updates @remix-run/react from 1.19.3 to 2.4.0

Release notes

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

v2.4.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v240

v2.3.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v231

v2.3.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v230

v2.2.0

Minor Changes

Vite!

Remix 2.2.0 adds unstable support for Vite for Node-based apps! See our announcement blog post and the Future > Vite page in the Remix docs for more details. (#7590)

You can try it out today with two new (unstable) templates:

# minimal server
npx create-remix@latest --template remix-run/remix/templates/unstable-vite

custom server (Express example)


npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express

New APIs in @remix-run/dev

  • unstable_vitePlugin: The new Remix Vite plugin
  • unstable_createViteServer: Creates a Vite server in middleware mode for interop with custom servers
  • unstable_loadViteServerBuild: Allows your custom server to delegate SSR requests to Vite during development

Changed APIs

  • createRequestHandler: Now also allows the build argument to be a function that will be used to dynamically load new builds for each request during development

Other Runtimes

  • Deno support is untested, but should work through Deno's Node/npm interop
  • CloudFlare support is not yet available

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors. (#10960)

  • You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
  • Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
  • Form and useSumbit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
    • <Form method="post" navigate={false} fetcherKey="my-key">
    • submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })

... (truncated)

Changelog

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

2.4.0

Minor Changes

  • Add support for clientLoader/clientAction/HydrateFallback route exports (RFC). (#8173)

    Remix now supports loaders/actions that run on the client (in addition to, or instead of the loader/action that runs on the server). While we still recommend server loaders/actions for the majority of your data needs in a Remix app - these provide some levers you can pull for more advanced use-cases such as:

    • Leveraging a data source local to the browser (i.e., localStorage)
    • Managing a client-side cache of server data (like IndexedDB)
    • Bypassing the Remix server in a BFF setup and hitting your API directly from the browser
    • Migrating a React Router SPA to a Remix application

    By default, clientLoader will not run on hydration, and will only run on subsequent client side navigations.

    If you wish to run your client loader on hydration, you can set clientLoader.hydrate=true to force Remix to execute it on initial page load. Keep in mind that Remix will still SSR your route component so you should ensure that there is no new required data being added by your clientLoader.

    If your clientLoader needs to run on hydration and adds data you require to render the route component, you can export a HydrateFallback component that will render during SSR, and then your route component will not render until the clientLoader has executed on hydration.

    clientAction is simpler than clientLoader because it has no hydration use-cases. clientAction will only run on client-side navigations.

    For more information, please refer to the clientLoader and clientAction documentation.

  • Add a new future.v3_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. For more information, please see the React Router 6.21.0 Release Notes and the useResolvedPath docs. (#8216)

Patch Changes

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

2.3.1

Patch Changes

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

2.3.0

Minor Changes

  • Remove the unstable_ prefix from the useBlocker hook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix from unstable_usePrompt due to differences in how browsers handle window.confirm that prevent React Router from guaranteeing consistent/correct behavior. (#7882)

Patch Changes

  • Support rendering of LiveReload component after Scripts in Vite dev (#7919)
  • Support optional rendering of LiveReload component in Vite dev (#7919)
  • add missing modulepreload for the manifest (#7684)
  • Updated dependencies:

... (truncated)

Commits

Updates @remix-run/serve from 1.19.3 to 2.4.0

Release notes

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

v2.4.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v240

v2.3.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v231

v2.3.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v230

v2.2.0

Minor Changes

Vite!

Remix 2.2.0 adds unstable support for Vite for Node-based apps! See our announcement blog post and the Future > Vite page in the Remix docs for more details. (#7590)

You can try it out today with two new (unstable) templates:

# minimal server
npx create-remix@latest --template remix-run/remix/templates/unstable-vite

custom server (Express example)


npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express

New APIs in @remix-run/dev

  • unstable_vitePlugin: The new Remix Vite plugin
  • unstable_createViteServer: Creates a Vite server in middleware mode for interop with custom servers
  • unstable_loadViteServerBuild: Allows your custom server to delegate SSR requests to Vite during development

Changed APIs

  • createRequestHandler: Now also allows the build argument to be a function that will be used to dynamically load new builds for each request during development

Other Runtimes

  • Deno support is untested, but should work through Deno's Node/npm interop
  • CloudFlare support is not yet available

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors. (#10960)

  • You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
  • Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
  • Form and useSumbit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
    • <Form method="post" navigate={false} fetcherKey="my-key">
    • submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })

... (truncated)

Changelog

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

2.4.0

Patch Changes

  • Fix source map loading when file has ?t=timestamp suffix (rebuilds) (#8174)
  • Updated dependencies:
    • @remix-run/node@2.4.0
    • @remix-run/express@2.4.0

2.3.1

Patch Changes

  • Updated dependencies:
    • @remix-run/express@2.3.1
    • @remix-run/node@2.3.1

2.3.0

Patch Changes

  • Updated dependencies:
    • @remix-run/express@2.3.0
    • @remix-run/node@2.3.0

2.2.0

Patch Changes

  • Updated dependencies:
    • @remix-run/express@2.2.0
    • @remix-run/node@2.2.0

2.1.0

Patch Changes

  • Updated dependencies:
    • @remix-run/express@2.1.0
    • @remix-run/node@2.1.0

2.0.1

Patch Changes

  • Fix HMR for CJS projects using remix-serve and manual mode (remix dev --manual) (#7487)
    • By explicitly busting the require cache, remix-serve now correctly re-imports new server changes in CJS
    • ESM projects were already working correctly and are not affected by this.
  • Fix error caused by partially written server build (#7470)
    • Previously, it was possible to trigger a reimport of the app server code before the new server build had completely been written. Reimporting the partially written server build caused issues related to build.assets being undefined and crashing when reading build.assets.version

... (truncated)

Commits

Updates @remix-run/dev from 1.19.3 to 2.4.0

Release notes

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

v2.4.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v240

v2.3.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v231

v2.3.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v230

v2.2.0

Minor Changes

Vite!

Remix 2.2.0 adds unstable support for Vite for Node-based apps! See our announcement blog post and the Future > Vite page in the Remix docs for more details. (#7590)

You can try it out today with two new (unstable) templates:

# minimal server
npx create-remix@latest --template remix-run/remix/templates/unstable-vite

custom server (Express example)


npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express

New APIs in @remix-run/dev

  • unstable_vitePlugin: The new Remix Vite plugin
  • unstable_createViteServer: Creates a Vite server in middleware mode for interop with custom servers
  • unstable_loadViteServerBuild: Allows your custom server to delegate SSR requests to Vite during development

Changed APIs

  • createRequestHandler: Now also allows the build argument to be a function that will be used to dynamically load new builds for each request during development

Other Runtimes

  • Deno support is untested, but should work through Deno's Node/npm interop
  • CloudFlare support is not yet available

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors. (#10960)

  • You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
  • Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
  • Form and useSumbit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
    • <Form method="post" navigate={false} fetcherKey="my-key">
    • submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })

... (truncated)

Changelog

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

2.4.0

Minor Changes

  • Vite: exclude modules within .server directories from client build (#8154)

  • Add support for clientLoader/clientAction/HydrateFallback route exports (RFC) (#8173)

    Remix now supports loaders/actions that run on the client (in addition to, or instead of the loader/action that runs on the server). While we still recommend server loaders/actions for the majority of your data needs in a Remix app - these provide some levers you can pull for more advanced use-cases such as:

    • Leveraging a data source local to the browser (i.e., localStorage)
    • Managing a client-side cache of server data (like IndexedDB)
    • Bypassing the Remix server in a BFF setup and hitting your API directly from the browser
    • Migrating a React Router SPA to a Remix application

    By default, clientLoader will not run on hydration, and will only run on subsequent client side navigations.

    If you wish to run your client loader on hydration, you can set clientLoader.hydrate=true to force Remix to execute it on initial page load. Keep in mind that Remix will still SSR your route component so you should ensure that there is no new required data being added by your clientLoader.

    If your clientLoader needs to run on hydration and adds data you require to render the route component, you can export a HydrateFallback component that will render during SSR, and then your route component will not render until the clientLoader has executed on hydration.

    clientAction is simpler than clientLoader because it has no hydration use-cases. clientAction will only run on client-side navigations.

    For more information, please refer to the clientLoader and clientAction documentation.

  • Vite: Strict route exports (#8171)

    With Vite, Remix gets stricter about which exports are allowed from your route modules. Previously, the Remix compiler would allow any export from routes. While this was convenient, it was also a common source of bugs that were hard to track down because they only surfaced at runtime.

    For more, see https://remix.run/docs/en/main/future/vite#strict-route-exports

  • Add a new future.v3_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. For more information, please see the React Router 6.21.0 Release Notes and the useResolvedPath docs. (#8216)

Patch Changes

  • Upgrade Vite peer dependency range to v5 (#8172)

  • Support HMR for routes with handle export in Vite dev (#8022)

  • Fix flash of unstyled content for non-Express custom servers in Vite dev (#8076)

  • Bundle CSS imported in client entry file in Vite plugin (#8143)

  • Change Vite build output paths to fix a conflict between how Vite and the Remix compiler each manage the public directory. (#8077)

    This is a breaking change for projects using the unstable Vite plugin.

    The server is now compiled into build/server rather than build, and the client is now compiled into build/client rather than public.

... (truncated)

Commits

Updates @remix-run/eslint-config from 1.19.3 to 2.4.0

Release notes

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

v2.4.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v240

v2.3.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v231

v2.3.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v230

v2.2.0

Minor Changes

Vite!

Remix 2.2.0 adds unstable support for Vite for Node-based apps! See our announcement blog post and the Future > Vite page in the Remix docs for more details. (#7590)

You can try it out today with two new (unstable) templates:

# minimal server
npx create-remix@latest --template remix-run/remix/templates/unstable-vite

custom server (Express example)


npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express

New APIs in @remix-run/dev

  • unstable_vitePlugin: The new Remix Vite plugin
  • unstable_createViteServer: Creates a Vite server in middleware mode for interop with custom servers
  • unstable_loadViteServerBuild: Allows your custom server to delegate SSR requests to Vite during development

Changed APIs

  • createRequestHandler: Now also allows the build argument to be a function that will be used to dynamically load new builds for each request during development

Other Runtimes

  • Deno support is untested, but should work through Deno's Node/npm interop
  • CloudFlare support is not yet available

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors. (#10960)

  • You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
  • Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
  • Form and useSumbit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
    • <Form method="post" navigate={false} fetcherKey="my-key">
    • submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })

... (truncated)

Changelog

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

2.4.0

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.4.0.

2.3.1

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.3.1.

2.3.0

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.3.0.

2.2.0

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v2.2.0.

2.1.0

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v2.1.0.

2.0.1

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v2.0.1.

2.0.0

Major Changes

  • Remove @remix-run/eslint-config/jest ESLint config (#6903)
  • Drop React 17 support (#7121)
  • Remove magic imports ESLint warnings (#6902)
  • Remove v2_normalizeFormMethod future flag - all formMethod values will be normalized in v2 (#6875)
Commits

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
@remix-run/serve [>= 0.21.a, < 0.22]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Dec 14, 2023
@dependabot dependabot bot mentioned this pull request Dec 14, 2023
Closed
@github-actions github-actions bot enabled auto-merge (rebase) December 14, 2023 08:02
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/remix-8bbdd7154d branch 5 times, most recently from b136f64 to bb064c5 Compare December 18, 2023 08:43
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/remix-8bbdd7154d branch 2 times, most recently from 74e7326 to 0eab9ab Compare December 18, 2023 19:24
@dependabot
Bump the remix group with 5 updates
8f5350e 
Bumps the remix group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [@remix-run/node](https://github.com/remix-run/remix/tree/HEAD/packages/remix-node) | `1.19.3` | `2.4.0` |
| [@remix-run/react](https://github.com/remix-run/remix/tree/HEAD/packages/remix-react) | `1.19.3` | `2.4.0` |
| [@remix-run/serve](https://github.com/remix-run/remix/tree/HEAD/packages/remix-serve) | `1.19.3` | `2.4.0` |
| [@remix-run/dev](https://github.com/remix-run/remix/tree/HEAD/packages/remix-dev) | `1.19.3` | `2.4.0` |
| [@remix-run/eslint-config](https://github.com/remix-run/remix/tree/HEAD/packages/remix-eslint-config) | `1.19.3` | `2.4.0` |


Updates `@remix-run/node` from 1.19.3 to 2.4.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.4.0/packages/remix-node)

Updates `@remix-run/react` from 1.19.3 to 2.4.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.4.0/packages/remix-react)

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

Updates `@remix-run/dev` from 1.19.3 to 2.4.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.4.0/packages/remix-dev)

Updates `@remix-run/eslint-config` from 1.19.3 to 2.4.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.4.0/packages/remix-eslint-config)

---
updated-dependencies:
- 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/serve"
  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 force-pushed the dependabot/npm_and_yarn/remix-8bbdd7154d branch from 0eab9ab to 8f5350e Compare December 18, 2023 19:28
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 18, 2023

Looks like these dependencies are up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Dec 18, 2023
auto-merge was automatically disabled December 18, 2023 19:37

Pull request was closed

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/remix-8bbdd7154d branch December 18, 2023 19:37
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
0 participants