Anatomy of a JavaScript/Node project.

01-directory-structure.md

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

• lib/ is intended for code that can run as-is
• src/ is intended for code that needs to be manipulated before it can be used
• build/ is for any scripts or tooling needed to build your project
• dist/ is for compiled modules that can be used with other systems.
• bin/ is for any executable scripts, or compiled binaries used with, or built from your module.
• test/ is for all of your project/module's test scripts
• unit/ is a sub-directory for unit tests
• integration/ is a sub-directory for integration tests
• env/ is for any environment that's needed for testing
• doc/ documentation files, include a README.md in the root and reference docs there.
• examples/ use case examples

lib & src

The difference in using lib vs src should be:

• lib if you can use node's require() directly
• src if you can not, or the file must otherwise be manipulated before use

If you are committing copies of module/files that are from other systems, the use of (lib|src)/vendor/(vendor-name)/(project-name)/ is suggested.

build

If you have scripts/tools that are needed in order to build your project, they should reside in the build directory. Examples include scripts to fetch externally sourced data as part of your build process. Another example would be using build/tasks/ as a directory for separating tasks in a project.

dist

If your project/module is to be built for use with other platforms (either directly in the browser), or in an AMD system (such as require.js), then these outputted files should reside under the dist directory.

It is recommended to use a (module)-(version).(platform).[min].js format for the files that output into this directory. For example foo-0.1.0.browser.min.js or foo-0.1.0.amd.js.

bin

The bin folder is for any system modules your package will use and/or generate.

• The compiled node_gyp output for your module's binary code.
• Pre-compiled platform binaries
• package.json/bin scripts for your module

/example directory for example files (npm docs: https://docs.npmjs.com/files/package.json#directoriesexample )

What about other files such as CSS files and font files? Should they be under lib (lib/css, lib/fonts)?

Thank you for the information! i have a personal Node.js project I've been meaning to better organize and this has helped me greatly. I still have one question specific to my problem though. If anyone more experienced with organizing projects could help me, it'd be lovely.

This project is a bot for my personal Discord server, and it has a few files I'm not sure where to put. i have a "main" index.js file, that loads up the modules i made (all in lib/), reads a file with it's key to log on, the .json's with data from the users it's interacted with, connects to the server and waits for a message. After it receives one, it sends it to the appropriate module to deal with it, and sends back any response the module told it to.

I'm just not sure where to put 'index.js', the bot info file, and the folder that contains the .json's. Should index.js go with the modules in lib/ or someplace else? should i put all of this info about the bot and it's previous interactions in a data/ folder or something like that? I'm really not sure, and even though this is just for myself and my friends, i'd like to start to do things in a more professional, organized fashion.

Where should I put .bat/.cmd files that are created by me and are needed in my app? Is /bin intended for include these files?

Is there a practice around whether you should commit build files to your repo if they are just the output of running your npm?

Wow, sorry... don't even remember writing this, lol... been a long while.

When I wrote this, was mostly considering stand alone libraries. If you're writing an application, I tend to use ./src for the app's source code... keeping most of the other conventions... for stylesheets, I tend to favor them with the components they're used with, and globals with any higher level wrapper components.

For cmd/bat files, yeah, I'd put them largely in bin or build respectively. I tend to favor using the package.json scripts section with npm, and have the respective JS files where they belong. I use shelljs a lot for command scripts.

as to BDD, /src/feature/FEATURE_SECTION is what I tend to use for applications, stand alone libraries a bit different.

Really happy I found this, I was doing maybe 4 of them, just by accident or logic, the same way. Now I get it right and not wonder, this is great info.

Say, if I extracted some helper/utility functions in the utility.js file, am I supposed to put it in the lib folder?

Where would you place .json files with a basic directory structure?

@AmaaelTyrneaMitore if utility.js is third party... I would use lib/3rd-party-name/utility.js .. preferably it's in npm, and just reference directly or possibly git reference.

@SheaButta depends on the use... if it's data to use with the application, I would probably use a data/ directory, then use an environment variable check to see if it's set and that directory exists, then fallback to a relative path based on src environment.

Could you please mention about utils/ folder

Could you please mention about utils/ folder

Not sure utils/ would fit in this framework, since lib/ already acts as a sort of utility functions container.

These things can be very opinionated and vague, but you managed to describe them in a very simple way. Well done.