glitchgrab 1.58.2 → 1.58.3
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/README.md +4 -0
- package/dist/index.js +1453 -690
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +1453 -690
- package/dist/index.mjs.map +1 -1
- package/dist/server.d.mts +11 -0
- package/dist/server.d.ts +11 -0
- package/dist/server.js +7 -2
- package/dist/server.js.map +1 -1
- package/dist/server.mjs +7 -2
- package/dist/server.mjs.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -715,6 +715,10 @@ hydrateRoot(document, <App />, {
|
|
|
715
715
|
|
|
716
716
|
Next.js does not expose `hydrateRoot` options, so App Router apps should use the `error.tsx` snippets above.
|
|
717
717
|
|
|
718
|
+
### Hydration errors (React #418 family)
|
|
719
|
+
|
|
720
|
+
Nothing to wire. In production the provider catches React #418/#419/#422/#423/#425 with the **component stack** React built for them (Next.js normally throws it away), the server HTML React replaced, any extension or Translate nodes found in the page, and fetch timing. The issue is labelled `gg:hydration` and its title names the element that mismatched. The same mismatch groups into one issue across pages, browsers and deploys. If your site serves source maps (`productionBrowserSourceMaps: true`), Glitchgrab also maps the stack to your source files, so the issue names the nearest component file too.
|
|
721
|
+
|
|
718
722
|
### captureError options
|
|
719
723
|
|
|
720
724
|
```ts
|