Best React Folder Structures | Beginner - Intermediate - Advanced 

Eu sou também sou BR e gosto muito dos videos do @PedroTech. Continue estudando bastante que com certeza vc vai realizar seu sonho de ir morar no Canada!!! Força irmão :)

Glad you are liking the videos! I am still learning more about AWS hahaha should make it as soon as I feel ready

Check the feature-sliced design, I use some patterns from it in my angular projects for example slicing components folder on entities, features, pages and always keeping everything near the feature. Cool thing

I came here to say exact this. Great thing he shared, because you commented. Now we all learned :D

I appreciate ur comment because it gives a different perspective to the topic :) Like i mentioned, there is no exact answer, specially cause every project/developer is different. When i made this video (a year ago), i was using my dev experience at my first 2 jobs as a basis. Both followed similar structures as i showed in the video. Now, i think more aligned to what u mentioned in ur comment! But like i said, both options are equally correct, it depends on how u and ur team like to code.

@@PedroTechnologies vertical slice became popular in big react applications, separating the project into modules based on ddd

Awesome! Thank you for watching

Not true anymore

images in the public folder her quite heavy because they are by-passed and not compressed by react

Hahaha appreciate it :)

Happy to hear I helped :)

Awesome, thank you!

Please read about PSR concept then you will get your answer :)

Thank you! I have some videos on typescript!

1) Hahaha yeah it is. I think its harder to go from beginner to intermediate than intermediate to advanced. 2) Yeah, but its just the routes. For example, when you have a home page, a login page, a profile page. I just put them in the pages folder. 3) I don't use redux hahaha but maybe I will learn it and make some videos on it :) 4) Planning on it ;) 5) I have some tutorials on it, but will definitely make more!

@@PedroTechnologies Have you any particular reason to not use Redux, can you share your thought about it

Throw those in a components folder in a src folder. More components, but not any more complexity.

Glad you liked it! I am not very experienced with redux so I don't know if I could make such video.

@@PedroTechnologies If you do not use Redux, what do you use for state management , my friends use Redux but I find it difficult to learn , could you do a video on what state management system you use ?

It is just a preference, some people like to have files with caps and folders with lower. I like both :)

That should go into another project, like a backend project using nodejs, express, and whatever db (usually mongodb).

Material Icon Theme

Here it is: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-oNlMrpnUSFE.html

useContext + useReducer pattern .It is kind like Redux, but easier to work and you do not need to install anything !

@@marcoonlinetv7769 Yes I've used the context API in my React projects to date, which has been fine for those smaller projects. My understanding (impression) was if you want to become a mid/senior level React JS developer, using and knowing Redux was essential as many companies use it.

@@137dylan I do not speaking about context.api. But context with reducers. This is future and redux is in slow decline

@@137dylan being senior is not about knowing redux, but rather than being able to learn new library in one weekend, it doesn't matter if is it redux, recoil, mobx or zustand, really

nowadays context with useReducer does the job that years before you could only achieve with redux or smth. I tend to avoid redux as much as I can, too.

context api + useReducer, probably

you can use context or react recoil

Brasil

This ^. I'm doing this for a client project and it has worked out wonderfully. Develop is extremely efficient and fast. Love TS

Hope you enjoy it!

@@PedroTechnologies Yes project structure is very important and best Project structure helps in testing, development as well as it's easy to maintain

Sorry about that hahaha I planned on posting the last ep tuesday. But since it is a deployment video, I want to set up everything and prepare prior to it in order for the video to have the least amoutnt of mistakes possible (deployment is really annoying hahaha). And bc I was overwhelmed with work from my job, I couldn't finish recording it monday or tuesday, so I made this quick video since a lot of you asked. Next video is the last ep of the series!

@@PedroTechnologies Thx man, we appreciate the hard wor!

I disagree! Although testing is very important, it is mostly important later on in their dev journey (closer to when you are applying for jobs). Thousands of beginners give up when they start because they get scared, so making them write tests would only make them more scared. I learned testing 1 or 2 months before getting my first react job (so like 5 months after I started learning it), and never had issues with it. But everybody is different, so it depends on the person :)

I understand ur point, but I respectfully disagree! I feel like there is a disconnect from very smart programmers to the rest of the coding community. Most programmers will find it EXTREMELY hard in the beginning, and a good amount of them will give up. My channel and videos are meant to help beginners move past this and start enjoying the process of learning. If I sat here and told them that they had to start testing since the beginning, I would be ignoring the struggle I went through when professors/courses told me the same. In my opinion, testing is not as important as finding your love/joy in programming, and it can easily be a burden if done right in the beginning. It does set good standards, but it doesn't matter if eventually the people learning will lose motivation and stop coding. In my opinion, testing comes later on in the journey, not when u are a senior dev, but when u start building stuff that will be used by other people (like an entry level job or a startup u are starting). Code doesn't need to have tests to be complete, code is code. Just because someone wrote bad code it doesn't mean it's not code. Also, I don't believe TDD is necessary for everyone, I personally leave my tests to the end of each component group/feature I add and it works great! This is an awesome topic to discuss :) I appreciate ur feedback!