effective-rsc 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LLMS.md +6 -3
- package/README.md +3 -3
- package/dist/client/application.js +8 -8
- package/dist/client/application.js.map +1 -1
- package/dist/client/browser-capabilities.d.ts +2 -9
- package/dist/client/browser-capabilities.js +3 -14
- package/dist/client/browser-capabilities.js.map +1 -1
- package/dist/client/navigation-api.js +5 -4
- package/dist/client/navigation-api.js.map +1 -1
- package/dist/dev/client.js +14 -1
- package/dist/dev/client.js.map +1 -1
- package/dist/dev/panel.d.ts +6 -0
- package/dist/dev/panel.js +55 -2
- package/dist/dev/panel.js.map +1 -1
- package/docs/03-advanced/02-client-navigation/index.md +6 -3
- package/package.json +1 -1
|
@@ -2,9 +2,12 @@
|
|
|
2
2
|
|
|
3
3
|
ERSC handles eligible document navigations through the browser Navigation API and
|
|
4
4
|
`NavigationPrecommitController`. There is no History API fallback. A browser missing either one
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
5
|
+
still hydrates Client Components and supports Server Functions and streamed current-page refreshes,
|
|
6
|
+
including HMR. Links use full-page navigation instead of the client router. Without JavaScript,
|
|
7
|
+
the server-rendered document retains working links and natively submitted forms.
|
|
8
|
+
|
|
9
|
+
Development reports a missing navigation API in the console and a dismissible development-panel
|
|
10
|
+
warning. The warning does not block interaction and is absent in production.
|
|
8
11
|
|
|
9
12
|
An intercepted Page navigation has two milestones:
|
|
10
13
|
|