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

fix(deps): update remix monorepo to v2.9.2 #9

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 16, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@remix-run/css-bundle (source) 2.7.2 -> 2.9.2 age adoption passing confidence
@remix-run/dev (source) 2.7.2 -> 2.9.2 age adoption passing confidence
@remix-run/eslint-config (source) 2.7.2 -> 2.9.2 age adoption passing confidence
@remix-run/node (source) 2.7.2 -> 2.9.2 age adoption passing confidence
@remix-run/react (source) 2.7.2 -> 2.9.2 age adoption passing confidence
@remix-run/serve (source) 2.7.2 -> 2.9.2 age adoption passing confidence

Release Notes

remix-run/remix (@​remix-run/css-bundle)

v2.9.2

Compare Source

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

v2.9.1

Compare Source

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.

v2.9.0

Compare Source

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.

v2.8.1

Compare Source

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.

v2.8.0

Compare Source

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

remix-run/remix (@​remix-run/dev)

v2.9.2

Compare Source

Patch Changes
  • Fix dest already exists error when running remix vite:build (#​9305)
  • Vite: Fix issue resolving critical CSS during development when route files are located outside of the app directory. (#​9194)
  • Remove @remix-run/node from Vite plugin's optimizeDeps.include list since it was unnecessary and resulted in Vite warnings when not depending on this package. (#​9287)
  • Clean up redundant ?client-route=1 imports in development (#​9395)
  • Ensure Babel config files are not referenced when applying the react-refresh Babel transform within the Remix Vite plugin (#​9241)
  • Updated dependencies:

v2.9.1

Compare Source

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:

v2.9.0

Compare Source

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:

v2.8.1

Compare Source

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:

v2.8.0

Compare Source

Minor Changes
  • Pass resolved viteConfig to Remix Vite plugin's buildEnd hook (#​8885)
Patch Changes
  • Mark Layout as browser safe route export in esbuild compiler (#​8842)
  • Vite: Silence build warnings when dependencies include "use client" directives (#​8897)
  • Vite: Fix serverBundles issue where multiple browser manifests are generated (#​8864)
  • Support custom Vite build.assetsDir option (#​8843)
  • Updated dependencies:
remix-run/remix (@​remix-run/eslint-config)

v2.9.2

Compare Source

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

v2.9.1

Compare Source

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.

v2.9.0

Compare Source

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.

v2.8.1

Compare Source

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.

v2.8.0

Compare Source

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

remix-run/remix (@​remix-run/node)

v2.9.2

Compare Source

Patch Changes
  • Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#​9372, #​9404)
  • Updated dependencies:

v2.9.1

Compare Source

Patch Changes

v2.9.0

Compare Source

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

v2.8.1

Compare Source

Patch Changes

v2.8.0

Compare Source

Patch Changes
remix-run/remix (@​remix-run/react)

v2.9.2

Compare Source

Patch Changes
  • Add undefined to useActionData type override (#​9322)
  • Allow a nonce to be set on single fetch stream transfer inline scripts (#​9364)
  • Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#​9372, #​9404)
  • Updated dependencies:

v2.9.1

Compare Source

Patch Changes

v2.9.0

Compare Source

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/@&#8203;remix-run/react/future/single-fetch.d.ts to include in your tsconfig.json
Patch Changes

v2.8.1

Compare Source

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

v2.8.0

Compare Source

Patch Changes
  • Fix the default root ErrorBoundary component so it leverages the user-provided Layout component (#​8859)
  • Fix the default root HydrateFallback component so it leverages any user-provided Layout component (#​8892)
  • Ensure @remix-run/react re-exports everything from react-router-dom for SPA mode (#​8929)
  • Updated dependencies:
remix-run/remix (@​remix-run/serve)

v2.9.2

Compare Source

Patch Changes

v2.9.1

Compare Source

Patch Changes

v2.9.0

Compare Source

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

v2.8.1

Compare Source

Patch Changes

v2.8.0

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/remix-monorepo branch 5 times, most recently from 3622abb to c67239a Compare February 16, 2024 13:44
@renovate renovate bot force-pushed the renovate/remix-monorepo branch 2 times, most recently from d305697 to 20fc06e Compare February 23, 2024 03:19
@renovate renovate bot changed the title fix(deps): update remix monorepo to v1.19.3 fix(deps): update remix monorepo to v1.19.3 - autoclosed Feb 23, 2024
@renovate renovate bot closed this Feb 23, 2024
@renovate renovate bot deleted the renovate/remix-monorepo branch February 23, 2024 03:21
@renovate renovate bot changed the title fix(deps): update remix monorepo to v1.19.3 - autoclosed fix(deps): update remix monorepo to v1.19.3 Feb 29, 2024
@renovate renovate bot reopened this Feb 29, 2024
@renovate renovate bot restored the renovate/remix-monorepo branch February 29, 2024 01:30
@renovate renovate bot changed the title fix(deps): update remix monorepo to v1.19.3 fix(deps): update remix monorepo to v2.8.0 Feb 29, 2024
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.8.0 fix(deps): update remix monorepo to v2.8.1 Mar 7, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from cd2888a to da139bc Compare March 7, 2024 18:50
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from da139bc to 36879b1 Compare April 23, 2024 17:24
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.8.1 fix(deps): update remix monorepo to v2.9.0 Apr 23, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 36879b1 to e8ffdcc Compare April 24, 2024 16:32
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.9.0 fix(deps): update remix monorepo to v2.9.1 Apr 24, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from e8ffdcc to 244a850 Compare May 10, 2024 19:11
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.9.1 fix(deps): update remix monorepo to v2.9.2 May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants