@veluai/velu 0.1.11 → 0.1.13

package/src/runtime/ErrorBoundary.jsx

@@ -1,54 +1,54 @@
-import React from 'react';
-import { ErrorCard } from 'velu-ui';
-import { extractMdxError } from '../lib/extract-mdx-error.js';
-import { CATEGORY_LABEL } from '../lib/issues.js';
-import { KNOWN_COMPONENTS } from '../lib/known-components.js';
-
-/**
- * Catches render-time errors from the current page (unknown component, a
- * component that threw on a bad prop, etc.) and renders a branded ErrorCard in
- * its place — leaving the surrounding chrome (header, sidebar, TOC) mounted.
- *
- * This is the CLIENT-side safety net: when the reader navigates (react-router,
- * no full reload) to a page that throws, the chrome stays put and only the
- * body shows the card. On a direct load / reload of a broken page the error
- * happens during SSR instead — React's renderToString doesn't recover through
- * error boundaries, so the dev server catches it there and serves the
- * full-page branded error (and logs it to the terminal).
- *
- * In `App.jsx` it's keyed by `pathname`, so navigating to another page (or
- * fixing the file and reloading) remounts it and clears the error.
- */
-export default class ErrorBoundary extends React.Component {
-  constructor(props) {
-    super(props);
-    this.state = { error: null };
-  }
-
-  static getDerivedStateFromError(error) {
-    return { error };
-  }
-
-  render() {
-    const { error } = this.state;
-    if (!error) return this.props.children;
-
-    const issue = extractMdxError(error, {
-      knownComponents: KNOWN_COMPONENTS,
-      file: this.props.file || null,
-    });
-    return (
-      <ErrorCard
-        label={CATEGORY_LABEL[issue.category] || issue.category}
-        title={issue.title}
-        file={issue.file}
-        line={issue.line}
-        column={issue.column}
-        frame={issue.frame}
-        detail={issue.detail}
-        hint={issue.hint}
-        suggestion={issue.suggestion}
-      />
-    );
-  }
-}
+import React from 'react';
+import { ErrorCard } from 'velu-ui';
+import { extractMdxError } from '../lib/extract-mdx-error.js';
+import { CATEGORY_LABEL } from '../lib/issues.js';
+import { KNOWN_COMPONENTS } from '../lib/known-components.js';
+
+/**
+ * Catches render-time errors from the current page (unknown component, a
+ * component that threw on a bad prop, etc.) and renders a branded ErrorCard in
+ * its place — leaving the surrounding chrome (header, sidebar, TOC) mounted.
+ *
+ * This is the CLIENT-side safety net: when the reader navigates (react-router,
+ * no full reload) to a page that throws, the chrome stays put and only the
+ * body shows the card. On a direct load / reload of a broken page the error
+ * happens during SSR instead — React's renderToString doesn't recover through
+ * error boundaries, so the dev server catches it there and serves the
+ * full-page branded error (and logs it to the terminal).
+ *
+ * In `App.jsx` it's keyed by `pathname`, so navigating to another page (or
+ * fixing the file and reloading) remounts it and clears the error.
+ */
+export default class ErrorBoundary extends React.Component {
+  constructor(props) {
+    super(props);
+    this.state = { error: null };
+  }
+
+  static getDerivedStateFromError(error) {
+    return { error };
+  }
+
+  render() {
+    const { error } = this.state;
+    if (!error) return this.props.children;
+
+    const issue = extractMdxError(error, {
+      knownComponents: KNOWN_COMPONENTS,
+      file: this.props.file || null,
+    });
+    return (
+      <ErrorCard
+        label={CATEGORY_LABEL[issue.category] || issue.category}
+        title={issue.title}
+        file={issue.file}
+        line={issue.line}
+        column={issue.column}
+        frame={issue.frame}
+        detail={issue.detail}
+        hint={issue.hint}
+        suggestion={issue.suggestion}
+      />
+    );
+  }
+}