scaffdog
react-error-boundary
scaffdog | react-error-boundary | |
---|---|---|
3 | 14 | |
669 | 6,420 | |
1.3% | - | |
9.5 | 6.8 | |
4 days ago | 2 months ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
scaffdog
react-error-boundary
-
Class vs functional components
I use the use-error-boundary module for this just to never have to write a class component myself!
-
You're in an interview for a react position and they ask you "which is better, functional or class based components" how would you answer?
Requires a dependency but you can absolutely use error boundaries with functional components via react-error-boundary: https://github.com/bvaughn/react-error-boundary
-
Is defining a function call inside a useEffect a good practice ?
as for checking errors: https://github.com/bvaughn/react-error-boundary
-
How to handle errors in React: full guide
For those of you, who hate re-inventing the wheel or just prefer libraries for already solved problems, there is a nice one that implements a flexible ErrorBoundary component and has a few useful utils similar to those described above: GitHub - bvaughn/react-error-boundary
-
I have an app written in old redux with React classes and try to migrate it to the latest version with hooks. What would you recommend to read/watch?
Use https://github.com/bvaughn/react-error-boundary for error boundaries and you won't have to write one yourself.
-
best way to convince OOPers to give functions a go?
There's no reason to manually write an error boundary as a class component yourself, either, given that https://github.com/bvaughn/react-error-boundary exists.
-
Should we use Functional or Class based Components?
Yeah, and even in that case, you should probably be using https://github.com/bvaughn/react-error-boundary rather than writing your own from scratch.
-
Should I still use class based components?
they can https://github.com/bvaughn/react-error-boundary (this is from the react team) doesn't matter how it works internally, im not going to write a class just for error handling.
- "bulletproof-react" is a hidden treasure of React best practices!
-
Derived State?
i would not bother with classes tbh, use this: https://github.com/bvaughn/react-error-boundary it's made by a react core team member and they even recommend it.
What are some alternatives?
naming-cheatsheet - Comprehensive language-agnostic guidelines on variables naming. Home of the A/HC/LC pattern.
react-hook-form - 📋 React Hooks for form state management and validation (Web + React Native)
Sentry - Developer-first error tracking and performance monitoring
nodejs-api-starter - 💥 Yarn v2 based monorepo template (seed project) pre-configured with GraphQL API, PostgreSQL, React, Relay, and Material UI. [Moved to: https://github.com/kriasoft/relay-starter-kit]
react-router - Declarative routing for React
create-mpl - ⚡️ Create a project in seconds!
tmpl-htm - Generate HTML elements using HTM ("Hyperscript Tagged Markup") or JSX.
redux-essentials-example-app - Example app for the Redux Essentials tutorial
Tailwind CSS - A utility-first CSS framework for rapid UI development.
usehooks - Easy to understand React Hook code recipes