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 #2077

Closed
wants to merge 1 commit into from
Closed

Bump the remix group with 5 updates #2077

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps the remix group with 5 updates:

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

Updates @remix-run/node from 1.19.3 to 2.3.1

Release notes

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

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" })
    • Invoking a fetcher in this way is ephemeral and stateless
    • If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

... (truncated)

Changelog

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

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:

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

... (truncated)

Commits

Updates @remix-run/react from 1.19.3 to 2.3.1

Release notes

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

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" })
    • Invoking a fetcher in this way is ephemeral and stateless
    • If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

... (truncated)

Changelog

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

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

2.2.0

Minor Changes

  • Unstable Vite support for Node-based Remix apps (#7590)
    • remix build 👉 vite build && vite build --ssr
    • remix dev 👉 vite dev
    • Other runtimes (e.g. Deno, Cloudflare) not yet supported.
    • See "Future > Vite" in the Remix Docs for details
  • Add a new future.v3_fetcherPersist flag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmounted in the UI, fetchers will persist until they return to an idle state (RFC) (#7704)

Patch Changes

  • Fix warning that could be logged when using route files with no default export (#7745)
    • It seems our compiler compiles these files to export an empty object as the default which we can then end up passing to React.createElement, triggering the console warning, but generally no UI issues
    • By properly detecting these, we can correctly pass Component: undefined off to the React Router layer
    • This is technically an potential issue in the compiler but it's an easy patch in the @remix-run/react layer and hopefully disappears in a Vite world
  • Fix critical CSS hydration errors for Vite dev (#7812)
  • Updated dependencies:

2.1.0

Minor Changes

... (truncated)

Commits

Updates @remix-run/serve from 1.19.3 to 2.3.1

Release notes

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

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" })
    • Invoking a fetcher in this way is ephemeral and stateless
    • If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

... (truncated)

Changelog

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

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
  • Updated dependencies:
    • @remix-run/node@2.0.1
    • @remix-run/express@2.0.1

2.0.0

Major Changes

  • remix-serve now picks an open port if 3000 is taken (#7278)

... (truncated)

Commits

Updates @remix-run/dev from 1.19.3 to 2.3.1

Release notes

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

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" })
    • Invoking a fetcher in this way is ephemeral and stateless
    • If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

... (truncated)

Changelog

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

2.3.1

Patch Changes

  • Support nonce prop on LiveReload component in Vite dev (#8014)
  • Ensure code-split JS files in the server build's assets directory aren't cleaned up after Vite build (#8042)
  • Fix redundant copying of assets from public directory in Vite build (#8039)
    • This ensures that static assets aren't duplicated in the server build directory
    • This also fixes an issue where the build would break if assetsBuildDirectory was deeply nested within the public directory
  • Updated dependencies:
    • @remix-run/node@2.3.1
    • @remix-run/server-runtime@2.3.1

2.3.0

Patch Changes

  • Support rendering of LiveReload component after Scripts in Vite dev (#7919)
  • fix(vite): fix "react-refresh/babel" resolution for custom server with pnpm (#7904)
  • Support JSX usage in .jsx files without manual React import in Vite (#7888)
  • Support optional rendering of LiveReload component in Vite dev (#7919)
  • Fix Vite production builds when plugins that have different local state between development and production modes are present, e.g. @mdx-js/rollup. (#7911)
  • Cache resolution of Remix Vite plugin options (#7908)
  • Support Vite 5 (#7846)
  • Allow process.env.NODE_ENV values other than "development" in Vite dev (#7980)
  • Attach CSS from shared chunks to routes in Vite build (#7952)
  • fix(vite): Let Vite handle serving files outside of project root via /@fs (#7913)
    • This fixes errors when using default client entry or server entry in a pnpm project where those files may be outside of the project root, but within the workspace root.
    • By default, Vite prevents access to files outside the workspace root (when using workspaces) or outside of the project root (when not using workspaces) unless user explicitly opts into it via Vite's server.fs.allow.
  • Improve performance of LiveReload proxy in Vite dev (#7883)
  • fix(vite): deduplicate @remix-run/react (#7926)
    • Pre-bundle Remix dependencies to avoid Remix router duplicates.
    • Our remix-react-proxy plugin does not process default client and
    • server entry files since those come from within node_modules.
    • That means that before Vite pre-bundles dependencies (e.g. first time dev server is run) mismatching Remix routers cause Error: You must render this element inside a <Remix> element.
  • Fix React Fast Refresh error on load when using defer in Vite dev server (#7842)
  • Handle multiple "Set-Cookie" headers in Vite dev server (#7843)
  • Fix flash of unstyled content on initial page load in Vite dev when using a custom Express server (#7937)
  • Emit assets that were only referenced in the server build into the client assets directory in Vite build (#7892, cherry-picked in 8cd31d65)
  • Populate process.env from .env files on the server in Vite dev (#7958)
  • Fix FutureConfig type (#7895)
  • Updated dependencies:
    • @remix-run/server-runtime@2.3.0
    • @remix-run/node@2.3.0

2.2.0

Minor Changes

  • Unstable Vite support for Node-based Remix apps (#7590)

... (truncated)

Commits

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

Release notes

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

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" })
    • Invoking a fetcher in this way is ephemeral and stateless
    • If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

... (truncated)

Changelog

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

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 9, 2023
@github-actions github-actions bot enabled auto-merge (rebase) December 9, 2023 08:05
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/remix-6769923c9f branch 16 times, most recently from bb46f97 to 0eb7218 Compare December 13, 2023 07:19
@dependabot
Bump the remix group with 5 updates
a20cc2e 
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.3.1` |
| [@remix-run/react](https://github.com/remix-run/remix/tree/HEAD/packages/remix-react) | `1.19.3` | `2.3.1` |
| [@remix-run/serve](https://github.com/remix-run/remix/tree/HEAD/packages/remix-serve) | `1.19.3` | `2.3.1` |
| [@remix-run/dev](https://github.com/remix-run/remix/tree/HEAD/packages/remix-dev) | `1.19.3` | `2.3.1` |
| [@remix-run/eslint-config](https://github.com/remix-run/remix/tree/HEAD/packages/remix-eslint-config) | `1.19.3` | `2.3.1` |


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

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

Updates `@remix-run/serve` from 1.19.3 to 2.3.1
- [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.3.1/packages/remix-serve)

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

Updates `@remix-run/eslint-config` from 1.19.3 to 2.3.1
- [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.3.1/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-6769923c9f branch from 0eb7218 to a20cc2e Compare December 13, 2023 07:21
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 14, 2023

Superseded by #2100.

@dependabot dependabot bot closed this Dec 14, 2023
auto-merge was automatically disabled December 14, 2023 08:02

Pull request was closed

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/remix-6769923c9f branch December 14, 2023 08:02
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