react-error-boundary
bulletproof-react
react-error-boundary | bulletproof-react | |
---|---|---|
14 | 250 | |
6,445 | 22,853 | |
- | - | |
6.8 | 5.0 | |
2 months ago | 6 days 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.
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.
bulletproof-react
-
Coding Snippets Dev Log (9/27/23)
Using -> this guide to help structure a project in a better way
-
Best File Structure
bulletproof react
-
Beware of teammates who refactor code based on personal taste without proper documentation or completeness. Sounds familiar.
Well I’d definitely have a file structure in place. I use bullet proof react as my go to. But I mean like…I’d say there’s probably 10 things causing 90% of the problems. So things like folder structure, yes, but also how long the files are, I mean…how enmeshed it all is…maybe the naming conventions.
-
My React Beginner Project
Follow this: https://github.com/alan2207/bulletproof-react
-
What's the best component / folder architecture for a project to scale?
Your approach is similar to bulletproof-react, which I personally love. I have built projects of all sizes with it and the DX was always nice! Check it out if you want and good luck on your project 😁
-
Are there any react js best practices websites?
Link for the lazy ones.
-
Inspiration for my first React project
Not sure if this helps, but Bulletproof React is a very good architecture to React projects of any size. Maybe it can give you some insight on how to structure your project. Good luck!
- Software Architecture in React
- Software Architecture in frontend
-
Best practices for organizing projects files in react
Been content with how Bulletproof react does it, only thing missing for me is differentiation between views and components.
What are some alternatives?
react-hook-form - 📋 React Hooks for form state management and validation (Web + React Native)
react-clean-architecture - A realistic approach to implement clean architecture on react codebases
Sentry - Developer-first error tracking and performance monitoring
documentation - 🍰 Architectural design methodology for Frontend projects
react-router - Declarative routing for React
excalidraw - Virtual whiteboard for sketching hand-drawn like diagrams
naming-cheatsheet - Comprehensive language-agnostic guidelines on variables naming. Home of the A/HC/LC pattern.
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
redux-essentials-example-app - Example app for the Redux Essentials tutorial
payload - The best way to build a modern backend + admin UI. No black magic, all TypeScript, and fully open-source, Payload is both an app framework and a headless CMS.
scaffdog - :dog: scaffdog is Markdown driven scaffolding tool.
SAAS-Starter-Kit-Pro - 🚀A boilerplate for building Software-as-Service (SAAS) apps with Reactjs, and Nodejs