How do you structure a feature module that has sub-features in NestJS?

Q: How do you structure a feature module that has sub-features in NestJS?

// Folder structure src/ users/ dto/ create-user.dto.ts entities/ user.entity.ts users.controller.ts users.service.ts users.module.ts // Barrel module with sub-modules @Module({ imports: [ UsersCoreModule, UserPreferencesModule, UserSessionsModule, ], exports: [UsersCoreModule], // expose only what external consumers need }) export class UsersModule {} One folder per domain feature — all related files live together. Create nested modules when a feature has multiple distinct sub-concerns. The parent barrel module controls the public surface via selective re-exports. Sub-modules can be independently tested without the parent barrel module. Avoid deep nesting beyond two levels — it adds complexity without much benefit.

Difficulty: 5/10

module organization, dynamic modules, dependency injection

Organize by domain subdirectory with a barrel module that imports sub-modules. Each sub-concern gets its own module. The parent module imports all sub-modules and re-exports only what external consumers need, keeping internals private.

Recommended folder layout and barrel module

Sub-feature structuring guidelines:

1
One folder per domain feature — all related files live together.
2
Create nested modules when a feature has multiple distinct sub-concerns.
3
The parent barrel module controls the public surface via selective re-exports.
4
Sub-modules can be independently tested without the parent barrel module.
5
Avoid deep nesting beyond two levels — it adds complexity without much benefit.

Scenario Questions

0-2 years experience

Follow-up Questions