When developing a Node.js application using Express.js, structuring your codebase effectively is... Tagged with webdev, javascript, beginners, programming.

Dark emperor

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

In Node.js applications using Express.js, effective codebase structuring is vital for maintainability, scalability, and easier collaboration. This guide outlines a common directory structure, explaining the purpose of each folder and file, from 'app.js' to 'node_modules', to help manage complexity and build robust applications.

How to Structure Your Backend Code in Node.js (Express.js)

Wouldn’t it be nice if we had a <code>src</code> directory? Which has all the sub-directories related to backend?

I was also struggling with the same issues, structuring the project, etc. Eventually, I decided to create Framework X.
please have a look, you might like it.
<a href="https://frameworkx.info/docs/introduction/" target="_blank" rel="noopener nofollow">https://frameworkx.info/docs/introduction/</a>

Nah, this is bad for searching files.
Don’t just name your controller, routes, etc. files for the “my-model” model “my-model.js”, now you have 600000 files with the same name in the project.
Add the name type after the model name, “my-model-controller.js”, “my-model-route.js”, “my-model-view.js”, etc.

When the project get bigger it will be hard to jump between the files in this structure.
I recommend doing a folder for every entity and inside we make a files entityNameRoute entityNameController entityNameSchema and so on.