{"id":39930222,"url":"https://github.com/rm-hull/chakra-error-fallback","last_synced_at":"2026-01-20T17:36:07.754Z","repository":{"id":321979834,"uuid":"1087836692","full_name":"rm-hull/chakra-error-fallback","owner":"rm-hull","description":"A type-safe React component for handling errors in Chakra UI applications, providing a fallback UI when something goes wrong.","archived":false,"fork":false,"pushed_at":"2026-01-12T07:47:36.000Z","size":2478,"stargazers_count":0,"open_issues_count":1,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-01-12T17:46:33.293Z","etag":null,"topics":["chakra-ui","error-handling","react","stack-trace"],"latest_commit_sha":null,"homepage":"https://www.destructuring-bind.org/chakra-error-fallback/","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/rm-hull.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2025-11-01T18:38:23.000Z","updated_at":"2026-01-12T07:47:38.000Z","dependencies_parsed_at":"2025-12-29T20:10:49.020Z","dependency_job_id":null,"html_url":"https://github.com/rm-hull/chakra-error-fallback","commit_stats":null,"previous_names":["rm-hull/chakra-error-fallback"],"tags_count":3,"template":false,"template_full_name":null,"purl":"pkg:github/rm-hull/chakra-error-fallback","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rm-hull%2Fchakra-error-fallback","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rm-hull%2Fchakra-error-fallback/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rm-hull%2Fchakra-error-fallback/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rm-hull%2Fchakra-error-fallback/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/rm-hull","download_url":"https://codeload.github.com/rm-hull/chakra-error-fallback/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rm-hull%2Fchakra-error-fallback/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28547004,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-18T14:59:57.589Z","status":"ssl_error","status_checked_at":"2026-01-18T14:59:46.540Z","response_time":98,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["chakra-ui","error-handling","react","stack-trace"],"created_at":"2026-01-18T18:06:50.913Z","updated_at":"2026-01-18T18:06:51.059Z","avatar_url":"https://github.com/rm-hull.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Chakra Error Fallback\n\n![NPM Version](https://img.shields.io/npm/v/@rm-hull/chakra-error-fallback)\n![Coveralls](https://img.shields.io/coverallsCoverage/github/rm-hull/chakra-error-fallback)\n![NPM Downloads](https://img.shields.io/npm/dm/@rm-hull/chakra-error-fallback)\n\nA type-safe React component for handling errors in Chakra UI applications, providing a fallback UI when something goes wrong.\n\n### Why use this?\n\n- **Graceful Error Handling** - Prevents your application from crashing and provides a user-friendly error message.\n- **Customizable** - Easily customize the appearance of the error fallback to match your application's theme.\n- **Developer Friendly** - Provides detailed error information in development mode to help with debugging.\n- **SSR Compatible** - Works seamlessly with server-side rendering.\n- **Expanded Stack Frames** - Stack frames are automatically expanded for better readability. This feature requires `build.sourcemap=true` in your Vite configuration to function correctly.\n- **Colorized Stack Traces** - Stack traces are colorized to improve readability and quickly identify different parts of the trace.\n\n## Quick Start\n\n```bash\nnpm install @rm-hull/chakra-error-fallback\n# or\nyarn add @rm-hull/chakra-error-fallback\n```\n\n## Basic Usage\n\nWrap your application or a part of it with the `ErrorBoundary` component from `react-error-boundary` and provide the `ErrorFallback` component to the `fallbackRender` prop.\n\n```tsx\nimport { ErrorBoundary } from \"react-error-boundary\";\nimport { ErrorFallback } from \"@rm-hull/chakra-error-fallback\";\nimport { ChakraProvider } from \"@chakra-ui/react\";\n\nfunction App() {\n  return (\n    \u003cChakraProvider\u003e\n      \u003cErrorBoundary FallbackComponent={ErrorFallback}\u003e\n        \u003cYourAppComponent /\u003e\n      \u003c/ErrorBoundary\u003e\n    \u003c/ChakraProvider\u003e\n  );\n}\n```\n\nSee the [**Storybook**](https://www.destructuring-bind.org/chakra-error-fallback) for further usage details.\n\n## Contributor Guidelines\n\n### Releasing a New Version\n\nThis project uses [**Changesets**](https://github.com/changesets/changesets) to manage versioning and automated npm publishing.\n\n#### How the release process works\n\n1.  **Create a changeset on your feature branch**\n\n    When you’ve made changes you want to release, first create a new branch (not on `main`):\n\n    ```bash\n    git checkout -b feature/my-change\n    ```\n\n    Make your changes, then run:\n\n    ```bash\n    yarn changeset\n    ```\n\n    You’ll be prompted to:\n\n    - Choose the type of version bump (patch, minor, or major)\n    - Write a short summary of the change\n\n    This command creates a markdown file in the `.changeset/` directory describing your upcoming release.\n\n2.  **Commit and push your feature branch**\n\n    ```bash\n    git add .\n    git commit -m \"feat: A short description of the change\"\n    git push -u origin feature/my-change\n    ```\n\n3.  **Merge the feature branch into `main`**\n\n    - Once your PR is reviewed, merge it into `main`. The `.changeset` file must be present in `main` for the next step.\n\n4.  **Automatic version bump and publish**\n\n    - When changes are pushed to `main`, GitHub Actions will automatically:\n\n      - Build the package\n      - Apply version bumps based on the `.changeset` file\n      - Update the changelog\n      - Publish the new version to npm as [`@rm-hull/chakra-error-fallback`](https://www.npmjs.com/package/@rm-hull/chakra-error-fallback)\n\n5.  **That's it!**\n    Your package is now live on npm with an updated version and changelog.\n\n---\n\n#### Notes\n\n- The npm publish step is automated via GitHub Actions (`.github/workflows/ci.yml`).\n- Ensure your `NPM_TOKEN` secret is configured in the repository settings under **Settings → Secrets → Actions**.\n- Changesets should always be created on feature branches, not directly on `main`.\n- No pull requests are created for version bumps; merging your feature branch into `main` triggers the release automatically.\n\n---\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frm-hull%2Fchakra-error-fallback","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Frm-hull%2Fchakra-error-fallback","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frm-hull%2Fchakra-error-fallback/lists"}