chore: Update version for release #8666
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
@remix-run/dev@2.6.0
Minor Changes
future.v3_throwAbortReason
flag to throwrequest.signal.reason
when a request is aborted instead of anError
such asnew Error("query() call aborted: GET /path")
(#8251)Patch Changes
Vite: Add
manifest
option to Vite plugin to enable writing a.remix/manifest.json
file to the build directory (#8575)This is a breaking change for consumers of the Vite plugin's "server bundles" feature.
The
build/server/bundles.json
file has been superseded by the more generalbuild/.remix/manifest.json
. While the old server bundles manifest was always written to disk when generating server bundles, the build manifest file must be explicitly enabled via themanifest
option.Vite: Provide
Unstable_ServerBundlesFunction
andUnstable_VitePluginConfig
types (#8654)Vite: add
--sourcemapClient
and--sourcemapServer
flags toremix vite:build
(#8613)--sourcemapClient
--sourcemapClient=inline
--sourcemapClient=hidden
--sourcemapServer
--sourcemapServer=inline
--sourcemapServer=hidden
See https://vitejs.dev/config/build-options.html#build-sourcemap
Vite: Validate IDs returned from the
serverBundles
function to ensure they only contain alphanumeric characters, hyphens and underscores (#8598)Vite: fix "could not fast refresh" false alarm (#8580)
HMR is already functioning correctly but was incorrectly logging that it "could not fast refresh" on internal client routes.
Now internal client routes correctly register Remix exports like
meta
for fast refresh,which removes the false alarm.
Vite: Cloudflare Pages support (#8531)
To get started with Cloudflare, you can use the [
unstable-vite-cloudflare
][template-vite-cloudflare] template:Or read the new docs at Future > Vite > Cloudflare and
Future > Vite > Migrating > Migrating Cloudflare Functions.
Vite: Remove undocumented backwards compatibility layer for Vite v4 (#8581)
Vite: rely on Vite plugin ordering (#8627)
This is a breaking change for projects using the unstable Vite plugin.
The Remix plugin expects to process JavaScript or TypeScript files, so any transpilation from other languages must be done first.
For example, that means putting the MDX plugin before the Remix plugin:
Previously, the Remix plugin misused
enforce: "post"
from Vite's plugin API to ensure that it ran last.However, this caused other unforeseen issues.
Instead, we now rely on standard Vite semantics for plugin ordering.
The official Vite React SWC plugin also relies on plugin ordering for MDX.
Vite: Add
presets
option to ease integration with different platforms and tools. (#8514)Vite: Remove interop with
<LiveReload />
, rely on<Scripts />
instead (#8636)This is a breaking change for projects using the unstable Vite plugin.
Vite provides a robust client-side runtime for development features like HMR,
making the
<LiveReload />
component obsolete.In fact, having a separate dev scripts component was causing issues with script execution order.
To work around this, the Remix Vite plugin used to override
<LiveReload />
into a bespokeimplementation that was compatible with Vite.
Instead of all this indirection, now the Remix Vite plugin instructs the
<Scripts />
componentto automatically include Vite's client-side runtime and other dev-only scripts.
Vite: Add
buildEnd
hook (#8620)Vite: add dev load context option to Cloudflare preset (#8649)
Vite: Add
mode
field into generated server build (#8539)Vite: Only write Vite manifest files if
build.manifest
is enabled within the Vite config (#8599)This is a breaking change for consumers of Vite's
manifest.json
files.To explicitly enable generation of Vite manifest files, you must set
build.manifest
totrue
in your Vite config.Vite: reduce network calls for route modules during HMR (#8591)
Vite: Add new
buildDirectory
option with a default value of"build"
. This replaces the oldassetsBuildDirectory
andserverBuildDirectory
options which defaulted to"build/client"
and"build/server"
respectively. (#8575)This is a breaking change for consumers of the Vite plugin that were using the
assetsBuildDirectory
andserverBuildDirectory
options.The Remix Vite plugin now builds into a single directory containing
client
andserver
directories. If you've customized your build output directories, you'll need to migrate to the newbuildDirectory
option, e.g.Vite: Remove
unstable
prefix fromserverBundles
option. (#8596)Vite: Write Vite manifest files to
build/.vite
directory rather than being nested withinbuild/client
andbuild/server
directories. (#8599)This is a breaking change for consumers of Vite's
manifest.json
files.Vite manifest files are now written to the Remix build directory. Since all Vite manifests are now in the same directory, they're no longer named
manifest.json
. Instead, they're namedbuild/.vite/client-manifest.json
andbuild/.vite/server-manifest.json
, orbuild/.vite/server-{BUNDLE_ID}-manifest.json
when using server bundles.Updated dependencies:
@remix-run/server-runtime@2.6.0
@remix-run/node@2.6.0
@remix-run/server-runtime@2.6.0
Minor Changes
future.v3_throwAbortReason
flag to throwrequest.signal.reason
when a request is aborted instead of anError
such asnew Error("query() call aborted: GET /path")
(#8251)Patch Changes
Vite: Cloudflare Pages support (#8531)
To get started with Cloudflare, you can use the [
unstable-vite-cloudflare
][template-vite-cloudflare] template:Or read the new docs at Future > Vite > Cloudflare and
Future > Vite > Migrating > Migrating Cloudflare Functions.
Unwrap thrown
Response
's fromentry.server
intoErrorResponse
's and preserve the status code (#8577)@remix-run/architect@2.6.0
Patch Changes
@remix-run/node@2.6.0
@remix-run/cloudflare@2.6.0
Patch Changes
@remix-run/server-runtime@2.6.0
@remix-run/cloudflare-pages@2.6.0
Patch Changes
Vite: Cloudflare Pages support (#8531)
To get started with Cloudflare, you can use the [
unstable-vite-cloudflare
][template-vite-cloudflare] template:Or read the new docs at Future > Vite > Cloudflare and
Future > Vite > Migrating > Migrating Cloudflare Functions.
Updated dependencies:
@remix-run/cloudflare@2.6.0
@remix-run/cloudflare-workers@2.6.0
Patch Changes
@remix-run/cloudflare@2.6.0
@remix-run/deno@2.6.0
Patch Changes
@remix-run/server-runtime@2.6.0
@remix-run/express@2.6.0
Patch Changes
@remix-run/node@2.6.0
@remix-run/node@2.6.0
Patch Changes
@remix-run/server-runtime@2.6.0
@remix-run/react@2.6.0
Patch Changes
@remix-run/server-runtime@2.6.0
@remix-run/serve@2.6.0
Patch Changes
@remix-run/node@2.6.0
@remix-run/express@2.6.0
@remix-run/testing@2.6.0
Patch Changes
@remix-run/react@2.6.0
@remix-run/node@2.6.0
create-remix@2.6.0
remix@2.6.0
remix
See the
CHANGELOG.md
in individual Remix packages for all changes.@remix-run/css-bundle@2.6.0
@remix-run/eslint-config@2.6.0