Open
Conversation
3fa2007 to
50e76bd
Compare
be6e230 to
5d5e6ee
Compare
27a9493 to
80d057a
Compare
630714b to
be3d8b8
Compare
3052db5 to
d2c369c
Compare
ec7d731 to
5ee2609
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 contains the following updates:
0.17.0→0.17.20.17.30.17.0→0.17.20.17.30.17.0→0.17.20.17.37.0.4→7.0.57.12.0→7.14.17.14.27.12.0→7.14.17.14.27.12.0→7.14.17.14.27.12.0→7.14.17.14.210.33.0→10.49.010.33.0→10.49.010.1.11→10.3.510.1.11→10.3.510.1.11→10.3.510.1.11→10.3.50.13.10→0.13.114.1.18→4.2.24.2.4(+1)8.16.0→8.20.019.2.8→19.2.1417.2.3→17.4.20.31.8→0.31.100.45.1→0.45.20.27.2→0.28.04.16.1→4.16.27.0.1→7.1.110.1.11→10.3.513.0.0→13.0.617.2.0→17.5.04.11.4→4.12.145.1.32→5.1.398.16.3→8.20.010.28.0→10.33.010.33.119.2.3→19.2.519.2.3→19.2.57.12.0→7.14.17.14.27.12.0→7.14.17.14.22.22.0→2.25.36.1.2→6.1.310.1.11→10.3.50.13.0→0.13.11.5→1.63.4.0→3.5.04.1.18→4.2.24.2.4(+1)8.53.0→8.58.28.59.0Release Notes
tursodatabase/libsql-client-ts (@libsql/client)
v0.17.2Compare Source
v0.17.1Compare Source
npm/package-json (@npmcli/package-json)
v7.0.5Compare Source
Bug Fixes
09b981d#172 inline license validation code (@wraithgar)Dependencies
cb3e677#172spdx-expression-parse@4.0.061738b2#172 remove validate-npm-package-licenseChores
bd3b7ea#169 bump @npmcli/template-oss from 4.28.0 to 4.28.1 (#169) (@dependabot[bot], @npm-cli-bot)remix-run/react-router (@react-router/dev)
v7.14.1Compare Source
Patch Changes
react-router@7.14.1@react-router/node@7.14.1@react-router/serve@7.14.1v7.14.0Compare Source
Minor Changes
Patch Changes
support for prerendering multiple server bundles with v8_viteEnvironmentApi (#14921)
rsc framework mode prerender / spa mode support (#14907)
UNSTABLE RSC FRAMEWORK MODE BREAKING CHANGE - Existing route module exports remain unchanged from stable v7 non-RSC mode, but new exports are added for RSC mode. If you want to use RSC features, you will need to update your route modules to export the new annotations. (#14901)
If you are using RSC framework mode currently, you will need to update your route modules to the new conventions. The following route module components have their own mutually exclusive server component counterparts:
ServerComponentdefaultServerErrorBoundaryErrorBoundaryServerLayoutLayoutServerHydrateFallbackHydrateFallbackIf you were previously exporting a
ServerComponent, yourErrorBoundary,Layout, andHydrateFallbackwere also server components. If you want to keep those as server components, you can rename them and prefix them withServer. If you were previously importing the implementations of those components from a client module, you can simply inline them.Example:
Before
After
update the reveal command to support rsc for
entry.client,entry.rsc,entry.ssr(#14904)Updated dependencies:
react-router@7.14.0@react-router/node@7.14.0@react-router/serve@7.14.0v7.13.2Compare Source
Patch Changes
Fix
react-router devcrash when Unix socket files exist in the project root (#14854)Escape redirect locations in prerendered redirect HTML (#14880)
Add
future.unstable_passThroughRequestsflag (#14775)By default, React Router normalizes the
request.urlpassed to yourloader,action, andmiddlewarefunctions by removing React Router's internal implementation details (.datasuffixes,index+_routesquery params).Enabling this flag removes that normalization and passes the raw HTTP
requestinstance to your handlers. This provides a few benefits:new Request()calls on the critical path.datasuffix (useful for observability purposes)If you were previously relying on the normalization of
request.url, you can switch to use the new siblingunstable_urlparameter which contains aURLinstance representing the normalized location:Add a new
unstable_url: URLparameter to route handler methods (loader,action,middleware, etc.) representing the normalized URL the application is navigating to or fetching, with React Router implementation details removed (.datasuffix,index/_routesquery params) (#14775)This is being added alongside the new
future.unstable_passthroughRequestsfuture flag so that users still have a way to access the normalized URL when that flag is enabled and non-normalizedrequest's are being passed to your handlers. When adopting this flag, you will only need to start leveraging this new parameter if you are relying on the normalization ofrequest.urlin your application code.If you don't have the flag enabled, then
unstable_urlwill matchrequest.url.Updated dependencies:
react-router@7.13.2@react-router/node@7.13.2@react-router/serve@7.13.2v7.13.1Compare Source
Patch Changes
react-router@7.13.1@react-router/node@7.13.1@react-router/serve@7.13.1v7.13.0Compare Source
Patch Changes
react-router@7.13.0@react-router/node@7.13.0@react-router/serve@7.13.0remix-run/react-router (@react-router/fs-routes)
v7.14.1Compare Source
Patch Changes
@react-router/dev@7.14.1v7.14.0Compare Source
Patch Changes
@react-router/dev@7.14.0v7.13.2Compare Source
Patch Changes
@react-router/dev@7.13.2v7.13.1Compare Source
Patch Changes
@react-router/dev@7.13.1v7.13.0Compare Source
Patch Changes
@react-router/dev@7.13.0remix-run/react-router (@react-router/node)
v7.14.1Compare Source
Patch Changes
react-router@7.14.1v7.14.0Compare Source
Patch Changes
react-router@7.14.0v7.13.2Compare Source
Patch Changes
react-router@7.13.2v7.13.1Compare Source
Patch Changes
react-router@7.13.1v7.13.0Compare Source
Patch Changes
react-router@7.13.0remix-run/react-router (@react-router/remix-routes-option-adapter)
v7.14.1Compare Source
Patch Changes
@react-router/dev@7.14.1v7.14.0Compare Source
Patch Changes
@react-router/dev@7.14.0v7.13.2Compare Source
Patch Changes
@react-router/dev@7.13.2v7.13.1Compare Source
Patch Changes
@react-router/dev@7.13.1v7.13.0Compare Source
Patch Changes
@react-router/dev@7.13.0getsentry/sentry-javascript (@sentry/profiling-node)
v10.49.0Compare Source
Important Changes
feat(browser): Add View Hierarchy integration (#14981)
A new
viewHierarchyIntegrationcaptures the DOM structure when an error occurs, providing a snapshot of the page state for debugging. Enable it in your Sentry configuration:feat(cloudflare): Split alarms into multiple traces and link them (#19373)
Durable Object alarms now create separate traces for each alarm invocation, with proper linking between related alarms for better observability.
feat(cloudflare): Enable RPC trace propagation with
enableRpcTracePropagation(#19991, #20345)A new
enableRpcTracePropagationoption enables automatic trace propagation for Cloudflare RPC calls via.fetch(), ensuring distributed traces flow correctly across service bindings.feat(core): Add
enableTruncationoption to AI integrations (#20167, #20181, #20182, #20183, #20184)All AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, LangGraph) now support an
enableTruncationoption to control whether large AI inputs/outputs are truncated.feat(opentelemetry): Vendor
AsyncLocalStorageContextManager(#20243)The OpenTelemetry context manager is now vendored internally, reducing external dependencies and ensuring consistent behavior across environments.
Other Changes
rewriteSourcestop level option (#20142)eventLoopBlockIntegration(#20108)conversation_idonly ongen_aispans (#20274)ai.operationIdfor Vercel AI V6 operation name mapping (#20285)reader.closedrejection fromreleaseLock()in streaming (#20187)Internal Changes
findInjectionIndexAfterDirectivesfor better readability (#20310)@opentelemetry/resourceswith inlinegetSentryResource()(#20327)Bundle size 📦
v10.48.0Compare Source
v10.47.0Compare Source
Important Changes
feat(node-core): Add OTLP integration for node-core/light (#19729)
Added
otlpIntegrationat@sentry/node-core/light/otlpfor users who managetheir own OpenTelemetry setup and want to send trace data to Sentry without
adopting the full
@sentry/nodeSDK.The integration links Sentry errors to OTel traces and exports spans to Sentry via OTLP.
feat(node, bun): Add runtime metrics integrations for Node.js and Bun (#19923, #19979)
New
nodeRuntimeMetricsIntegrationandbunRuntimeMetricsIntegrationautomatically collect runtime health metrics and send them to Sentry on a configurable interval (default: 30s). Collected metrics include memory (RSS, heap used/total), CPU utilization, event loop utilization, and process uptime. Node additionally collects event loop delay percentiles (p50, p99). Extra metrics like CPU time and external memory are available as opt-in.feat(core): Support embedding APIs in google-genai (#19797)
Adds instrumentation for the Google GenAI
embedContentAPI, creatinggen_ai.embeddingsspans.feat(browser): Add
elementTimingIntegrationfor tracking element render and load times (#19869)The new
elementTimingIntegrationcaptures Element Timing API data as Sentry metrics. It emitselement_timing.render_timeandelement_timing.load_timedistribution metrics for elements annotated with theelementtimingHTML attribute.Other Changes