Interesting...
I have a similar approach. Would be very interesting to see the structure inside of /components. Is there any nesting? A folder for each component with styles/test/... next to the component file itself? A single index.ts to re-export all components? Or a index.tsx in every components folder?
As you can see, I think there are many different approaches to the /components folder. Would love a followup article or edit on that.
Do you have any project where you applied that structure, that you can share? Would be interested in some API files.
I'm a software engineer with a lot of React and startup experience. I write about my opinions on React, using Firebase with React, and lessons from building my 1st startup, Retro.
Interesting...
I have a similar approach. Would be very interesting to see the structure inside of
/components
. Is there any nesting? A folder for each component with styles/test/... next to the component file itself? A singleindex.ts
to re-export all components? Or aindex.tsx
in every components folder?As you can see, I think there are many different approaches to the
/components
folder. Would love a followup article or edit on that.Do you have any project where you applied that structure, that you can share? Would be interested in some API files.
Thanks :)
I don't use any nesting in any of the folders. The shape of of my components folder is like so:
I usually don’t have styles files in my apps. I use plain css frameworks like tailwind or bootstrap so there is not a separate styles file.