Ever dreamt of a React app that chuckles at bugs and scoffs at spaghetti code? Let’s embark on a... Tagged with react, webdev, javascript, frontend.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

Learn how to structure your React projects for better organization and clarity. Use absolute imports for cleaner and more readable import statements. Use the index.ts file as the public API of each feature.

How I Structure my React Projects

Great read! I wish the index file portion was more detailed but overall this was a good article.

An experienced dev wouldn’t use create react app in the first place

For big projects you want to organize your code into domains / features instead of top-level utility-based folder structure.
That would add an extra dir level, e.g.:
<pre><code class="language-yaml">├─ src
│ ├─ orders
│ │ └─ assets 
│ │ └─ components 
│ │ └─ config 
│ │ └─ ... 
│ ├─ products
│ │ └─ assets 
│ │ └─ components 
│ │ └─ config 
│ │ └─ ... 
│ └─ utils 
</code></pre>

Well, good enough, but I saw over time that it also depends on what are you working. Also, if you code on business project, you need to follow company rules, which can be sometime quite strange

Suggest some best source to learn React js nd Next js