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

chore: Update version for release #7841

Merged
merged 2 commits into from
Oct 31, 2023
Merged

chore: Update version for release #7841

merged 2 commits into from
Oct 31, 2023

Conversation

github-actions[bot]
Copy link
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.

Releases

[email protected]

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.
    Custom server (e.g. Express) not yet supported.

    See "Future > Vite" in the Remix Docs for details.

Patch Changes

  • Support local tarballs with .tgz extension (#7649)

    It allows to directly support pnpm pack tarballs.

  • Set default Remix version to match the version of create-remix being used. This most notably enables easier usage of tags, e.g. npm create remix@nightly. (#7670)

@remix-run/[email protected]

Minor Changes

  • Add a new future.v3_fetcherPersist flag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmoutned in the UI, fetchers will persist until they return to an idle state (RFC) (#7704)

    • This is sort of a long-standing "bug fix" as the useFetchers() API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an idle state
    • Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:
      • Fetchers that complete while still mounted will no longer appear in useFetchers(). They served effectively no purpose in there since you can access the data via useFetcher().data).
      • Fetchers that previously unmounted while in-flight will not be immediately aborted and will instead be cleaned up once they return to an idle state. They will remain exposed via useFetchers while in-flight so you can still access pending/optimistic data after unmount.

  • 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.
    Custom server (e.g. Express) not yet supported.

    See "Future > Vite" in the Remix Docs for details.

Patch Changes

@remix-run/[email protected]

Minor Changes

  • Add a new future.v3_fetcherPersist flag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmoutned in the UI, fetchers will persist until they return to an idle state (RFC) (#7704)

    • This is sort of a long-standing "bug fix" as the useFetchers() API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an idle state
    • Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:
      • Fetchers that complete while still mounted will no longer appear in useFetchers(). They served effectively no purpose in there since you can access the data via useFetcher().data).
      • Fetchers that previously unmounted while in-flight will not be immediately aborted and will instead be cleaned up once they return to an idle state. They will remain exposed via useFetchers while in-flight so you can still access pending/optimistic data after unmount.

  • 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.
    Custom server (e.g. Express) not yet supported.

    See "Future > Vite" in the Remix Docs for details.

Patch Changes

  • Lock into react router stable versions (#7838)

  • 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)

  • [REMOVE] bump to latest router prerelease (#7825)

  • Updated dependencies:

@remix-run/[email protected]

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.
    Custom server (e.g. Express) not yet supported.

    See "Future > Vite" in the Remix Docs for details.

@remix-run/[email protected]

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.
    Custom server (e.g. Express) not yet supported.

    See "Future > Vite" in the Remix Docs for details.

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

  • Allow the @remix-run/express adapter to work behind a proxy when using app.enable('trust proxy') (#7323)

    • Previously, this used req.get('host') to construct the Remix Request, but that does not respect X-Forwarded-Host
    • This now uses req.hostname which will respect X-Forwarded-Host

  • Updated dependencies:

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

[email protected]

remix

See the CHANGELOG.md in individual Remix packages for all changes.

@remix-run/[email protected]

@remix-run/[email protected]

[email protected]

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.
    Custom server (e.g. Express) not yet supported.

    See "Future > Vite" in the Remix Docs for details.

@github-actions github-actions bot force-pushed the changeset-release/release-next branch from 2671a7b to e37e4e0 Compare October 31, 2023 15:14
@brophdawg11 brophdawg11 merged commit 85caf9b into release-next Oct 31, 2023
9 checks passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch October 31, 2023 15:54
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
CLA Signed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@brophdawg11