Reuse module in npm package

[ ] Regression
[x] Bug report
[ ] Feature request
[x] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Hi all, I am using Nest for the past year and I love it, kudos for the team!

I have a question and maybe a bug… I am trying to reuse my code in separate repos…

I have a npm package with one module “CommonModule”. In that module I have a controller “MetadataController” and a service “MetadataService”.

Then I have my App that uses that module, but when I include the import CommonModule into the AppModule I have an error:

Error Nest cannot export a component/module that is not a part of the currently processed module (CommonModule). Please verify whether each exported unit is available in this particular context.

common.module:

import { Module } from '@nestjs/common';
import { MetadataController } from './controllers/metadata/metadata.controller';
import { MetadataService } from './services/metadata/metadata.service';

@Module({
  imports: [],
  controllers: [MetadataController],
  providers: [MetadataService],
  exports: [MetadataService],
})
export class CommonModule {}

app.module:

import { CommonModule } from 'my-repo';

@Module({
  imports: [
    CommonModule,
    TypeOrmModule.forRoot(AppModule.getTypeORMConfig()),
    GraphQLModule.forRoot({
      typePaths: ['./src/**/*.graphql'],
      definitions: {
        path: join(
          process.cwd(),
          './src/modules/generated-models/graphql-models.ts',
        ),
        outputAs: 'interface',
      },
      debug: true,
      playground: true,
    }),
  ],
  controllers: [],
  providers: [],
})

Expected behavior

It should be possible to reuse the module.

What is the motivation / use case for changing the behavior?

Reuse modules in external repos.

Environment

Nest version: 5.7.4
 
For Tooling issues:
- Node version: 11.0.0 
- Platform:  Linux

[kamilmysliwiec]

Remove & reinstall all packages. Your npm packages should only define peerDependencies - they shouldn’t have @nestjs/{x} defined inside dependencies so they can share packages among themselves.

[kamilmysliwiec]

You should make @nestjs/common and other @nestjs/{x} packages peer dependencies, so they can share metadata each other.