bulletproof-react VS documentation

Using -> this guide to help structure a project in a better way

bulletproof react

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.

Follow this: https://github.com/alan2207/bulletproof-react

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 😁

Link for the lazy ones.

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!

Been content with how Bulletproof react does it, only thing missing for me is differentiation between views and components.

Have you heard about Feature-Sliced Design? I have personally found it extremely helpful as the project grows larger, though it can have a bit of a learning curve

In our case, the current folder structure resembles Feature-Sliced Design:

Feature-slice design is the one and only correct solution imho

(https://feature-sliced.design/)

for large spa I recommend https://feature-sliced.design/

There are many more benefits of using feature sliced design which are well documented in the docs. I highly recommend you to check it out and learn new ways of organizing your frontend project.

Hi, I use feature-sliced design for big or middle spa. Excellent solution for scalability! https://feature-sliced.design/

Ссылка на офф сайт.

You can also see a way around this restriction in "DDD, Hexagonal, Onion, Clean, CQRS, ... How I put it all together" and Feature Sliced.