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.

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

chore(deps): bump the remix group across 1 directory with 6 updates #64

Merged
merged 2 commits into from
Apr 25, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 25, 2024

Bumps the remix group with 6 updates in the /web directory:

Package From To
@remix-run/node 2.8.0 2.9.1
@remix-run/react 2.8.0 2.9.1
@vercel/remix 2.8.1-patch.2 2.9.0
@remix-run/dev 2.8.0 2.9.1
@remix-run/eslint-config 2.8.0 2.9.1
@remix-run/serve 2.8.0 2.9.1

Updates @remix-run/node from 2.8.0 to 2.9.1

Release notes

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

v2.9.1

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

v2.9.0

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

v2.8.1

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

Changelog

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

2.9.1

Patch Changes

2.9.0

Minor Changes

  • Use undici as our fetch polyfill going forward (#9106, #9111)
  • Put undici fetch polyfill behind a new installGlobals({ nativeFetch: true }) parameter (#9198)
    • remix-serve will default to using undici for the fetch polyfill if future._unstable_singleFetch is enabled because the single fetch implementation relies on the undici polyfill
      • Any users opting into Single Fetch and managing their own polfill will need to pass the flag to installGlobals on their own to avoid runtime errors with Single Fetch

Patch Changes

2.8.1

Patch Changes

Commits

Updates @remix-run/react from 2.8.0 to 2.9.1

Release notes

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

v2.9.1

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

v2.9.0

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

v2.8.1

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

Changelog

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

2.9.1

Patch Changes

2.9.0

Minor Changes

  • New future.unstable_singleFetch flag (#8773)

    • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
    • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
      • If you need to return a custom status code or custom response headers, you can still use the defer utility
    • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
      • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
    • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate
  • Opt-in types for single-fetch (#9272)

    • To opt-in to type inference for single-fetch, add ./node_modules/@remix-run/react/future/single-fetch.d.ts to include in your tsconfig.json

Patch Changes

2.8.1

Patch Changes

  • Strengthen the internal LayoutComponent type to accept limited children (#8910)
  • Updated dependencies:
Commits

Updates @vercel/remix from 2.8.1-patch.2 to 2.9.0

Changelog

Sourced from @​vercel/remix's changelog.

v2.9.0

Date: 2024-04-23

What's Changed

Single Fetch (unstable)

2.9.0 introduces a future.unstable_singleFetch flag to enable to Single Fetch behavior (RFC) in your Remix application. Please refer to the docs for the full detail but the high-level changes to be aware of include:

  • Naked objects returned from loader/action functions are no longer automatically serialized to JSON responses
    • Instead, they'll be streamed as-is via turbo-stream which allows direct serialization of more complex types such as Promise, Date, Map instances, and more
    • You will need to modify your tsconfig.json's include array to infer types properly when using Single Fetch
  • The headers export is no longer used when Single Fetch is enabled in favor of a new response stub passed to your loader/action functions
  • The json/defer/redirect utilities are deprecated when using Single Fetch (but still work mostly the same)
  • Actions no longer automatically revalidate on 4xx/5xx responses - you can return a 2xx to opt-into revalidation or use shouldRevalidate

[!IMPORTANT] Single Fetch requires using undici as your fetch polyfill, or using the built-in fetch on Node 20+, because it relies on APIs available there but not in the @remix-run/web-fetch polyfill. Please refer to the Undici section below for more details.

  • If you are managing your own server and calling installGlobals(), you will need to call installGlobals({ nativeFetch: true }) to avoid runtime errors when using Single Fetch
  • If you are using remix-serve, it will use undici automatically if Single Fetch is enabled

Undici

Remix 2.9.0 adds a new installGlobals({ nativeFetch: true }) flag to opt into using undici for the Web Fetch polyfills instead of the @remix-run/web-* packages. This change has a few primary benefits:

  • It will allow us to stop maintaining our own web-std-io fork in future versions of Remix
  • It should bring us more in-line with spec compliance
    • ⚠️ It is possible that some non-spec-compliant bugs in our fork will be "fixed" by moving to undici, so beware of "breaking bug fixes" and keep an eye on any advanced fetch API interactions you're performing in your app
    • ⚠️ In some cases, undici may have different behavior by design -- most notably, undici's garbage collection behavior differs and you are required to consume all fetch response bodies to avoid a memory leak in your app
  • Because undici is the fetch implementation used by node internally, it should better prepare Remix apps to more smoothly drop the polyfill to use the built-in Node.js APIs on node 20+

Minor Changes

  • New future.unstable_singleFetch flag (#8773, #9073, #9084, #9272)
  • @remix-run/node - Add a new installGlobals({ nativeFetch: true }) flag to opt-into using undici as the fetch polyfill instead of @remix-run/web-* (#9106, #9111, #9198)
  • @remix-run/server-runtime - Add ResponseStub header interface and deprecate the headers export when Single Fetch is enabled (#9142)

Patch Changes

  • create-remix - Allow . in repo name when using --template flag (#9026)
  • @remix-run/dev - Improve getDependenciesToBundle resolution in monorepos (#8848)
  • @remix-run/dev - Fix SPA mode when Single Fetch is enabled by using streaming entry.server (#9063)
  • @remix-run/dev - Vite: added sourcemap support for transformed routes (#8970)
  • @remix-run/dev - Update links printed to the console by the Remix CLI/Dev Server to point to updated docs locations (#9176)
  • @remix-run/server-runtime - Handle redirects created by handleDataRequest (#9104)

Updated Dependencies

... (truncated)

Commits

Updates @remix-run/dev from 2.8.0 to 2.9.1

Release notes

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

v2.9.1

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

v2.9.0

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

v2.8.1

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

Changelog

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

2.9.1

Patch Changes

  • Fix issue where consumers who had added Remix packages to Vite's ssr.noExternal option were being overridden by the Remix Vite plugin adding Remix packages to Vite's ssr.external option (#9301)
  • Updated dependencies:

2.9.0

Minor Changes

  • New future.unstable_singleFetch flag (#8773)

    • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
    • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
      • If you need to return a custom status code or custom response headers, you can still use the defer utility
    • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
      • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
    • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

  • Improve getDependenciesToBundle resolution in monorepos (#8848)
  • Fix SPA mode when single fetch is enabled by using streaming entry.server (#9063)
  • Vite: added sourcemap support for transformed routes (#8970)
  • Update links printed to the console by the Remix CLI/Dev Server to point to updated docs locations (#9176)
  • Updated dependencies:

2.8.1

Patch Changes

  • Support reading from Vite config when running remix reveal and remix routes CLI commands (#8916)
  • Add Vite commands to Remix CLI --help output (#8939)
  • Vite: Fix support for build.sourcemap option in Vite config (#8965)
  • Clean up redundant client route query strings on route JavaScript files in production builds (#8969)
  • Vite: Fix error when using Vite's server.fs.allow option without a client entry file (#8966)
  • Updated dependencies:
Commits

Updates @remix-run/eslint-config from 2.8.0 to 2.9.1

Release notes

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

v2.9.1

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

v2.9.0

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

v2.8.1

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

Changelog

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

2.9.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.9.1.

2.9.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.9.0.

2.8.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.8.1.

Commits

Updates @remix-run/serve from 2.8.0 to 2.9.1

Release notes

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

v2.9.1

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

v2.9.0

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

v2.8.1

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

Changelog

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

2.9.1

Patch Changes

2.9.0

Minor Changes

  • Put undici fetch polyfill behind a new installGlobals({ nativeFetch: true }) parameter (#9198)
    • remix-serve will default to using undici for the fetch polyfill if future.unstable_singleFetch is enabled because the single fetch implementation relies on the undici polyfill
    • Any users opting into Single Fetch and managing their own polyfill will need to pass the flag to installGlobals on their own to avoid runtime errors with Single Fetch

Patch Changes

2.8.1

Patch Changes

Commits

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

Bumps the remix group with 6 updates in the /web directory:

| Package | From | To |
| --- | --- | --- |
| [@remix-run/node](https://github.com/remix-run/remix/tree/HEAD/packages/remix-node) | `2.8.0` | `2.9.1` |
| [@remix-run/react](https://github.com/remix-run/remix/tree/HEAD/packages/remix-react) | `2.8.0` | `2.9.1` |
| [@vercel/remix](https://github.com/vercel/remix/tree/HEAD/packages/vercel-remix) | `2.8.1-patch.2` | `2.9.0` |
| [@remix-run/dev](https://github.com/remix-run/remix/tree/HEAD/packages/remix-dev) | `2.8.0` | `2.9.1` |
| [@remix-run/eslint-config](https://github.com/remix-run/remix/tree/HEAD/packages/remix-eslint-config) | `2.8.0` | `2.9.1` |
| [@remix-run/serve](https://github.com/remix-run/remix/tree/HEAD/packages/remix-serve) | `2.8.0` | `2.9.1` |



Updates `@remix-run/node` from 2.8.0 to 2.9.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/[email protected]/packages/remix-node)

Updates `@remix-run/react` from 2.8.0 to 2.9.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/[email protected]/packages/remix-react)

Updates `@vercel/remix` from 2.8.1-patch.2 to 2.9.0
- [Changelog](https://github.com/vercel/remix/blob/main/CHANGELOG.md)
- [Commits](https://github.com/vercel/remix/commits/HEAD/packages/vercel-remix)

Updates `@remix-run/dev` from 2.8.0 to 2.9.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/[email protected]/packages/remix-dev)

Updates `@remix-run/eslint-config` from 2.8.0 to 2.9.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/[email protected]/packages/remix-eslint-config)

Updates `@remix-run/serve` from 2.8.0 to 2.9.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/[email protected]/packages/remix-serve)

---
updated-dependencies:
- dependency-name: "@remix-run/node"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: remix
- dependency-name: "@remix-run/react"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: remix
- dependency-name: "@vercel/remix"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: remix
- dependency-name: "@remix-run/dev"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: remix
- dependency-name: "@remix-run/eslint-config"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: remix
- dependency-name: "@remix-run/serve"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: remix
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Dependencies updates web Website labels Apr 25, 2024
Copy link

vercel bot commented Apr 25, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
stats ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 25, 2024 8:56am

@olros olros merged commit 4e7d38c into main Apr 25, 2024
3 of 4 checks passed
@olros olros deleted the dependabot/npm_and_yarn/web/remix-715732e482 branch April 25, 2024 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Dependencies updates web Website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant