You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: GOVERNANCE.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,6 +164,32 @@ This section captures the notes from the React Router Steering Committee meeting
164
164
</details>
165
165
-->
166
166
167
+
<details>
168
+
<summary>2025-09-23 Meeting Notes</summary>
169
+
170
+
**Summary**
171
+
172
+
Brooks Lybrand announced the planned release of unstable framework RSC support in 7.9.2 and the `fetcher.unstable_reset()` API. Matt Brophy and Pedro Cattori discussed splitting Ryan's proposal for `useRouteLoaderData` type-safety to separate "router data" from "route data." Bryan Ross (rossipedia) and Matt Brophy reviewed the proposal for new instrumentation APIs. Matt Brophy and Jacob Ebey decided to close several issues related to ESLint configuration, OpenTelemetry, and module federation.
173
+
174
+
**Details**
175
+
176
+
- 7.9.2 will contain unstable support for RSC framework mode as well as the `fetcher.unstable_reset()` API
177
+
- The team reviewed the current instrumentation POC implementation:
- Current `instrumentRouter`/`instrumentRoutes` APIs should be sufficient for various implementations of logging/tracing layered on top
181
+
- React Router docs can show simple examples of a few types of observability implementations (logging, OTEL, `performance.mark`/`measure`), but will lean on the community to provide packages for specific observability approaches
182
+
- Jacob raised a good point about the design of the current APIs permitting more than instrumentation because folks could mutate existing handler parameters, so Matt is going to look into ways top provide a subset of read-only information that will prohibit this since it is not an intended use case and would likely be abused in unforeseen ways
183
+
- Matt Brophy will also play around with potential instrumentation utils to see if it is worth shipping anything or just putting them in documentation
184
+
- The committee reviewed and agreed to move forward 2 new RFCs to the "consideration" stage:
- Matt Brophy will comment back on the ESLint issue to get it closed out and point to the OpenTelemetry issue to the new instrumentation approach
188
+
- Pedro Cattori will start on the route stuff and try to get a PR up for it, once a PR is opened we will also get an issue on the roadmap
189
+
- Jacob Ebey will check in with Zach about his interest in the [current work w.r.t. module imoports](https://github.com/remix-run/react-router/pull/12638), and Matt Brophy will add a comment to the issue asking if it is needed and close it if there is no response in a week.
0 commit comments