feat(core): Add abortOnError option in NestApplicationContextOptions

[princechauhan1992]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

#5162

Issue Number: 5162

What is the new behavior?

An abortOnError flag is added in nestApplicationContext. By default the process is aborted, but if abortOnError is set to false,
error is rethrown instead of calling process.abort() or process.exit(1)

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[princechauhan1992]

@kamilmysliwiec This is my first contribution to an open source project, so I apologize in advance in case I have made any mistakes. Kindly suggest if any changes are required.

[coveralls]

Pull Request Test Coverage Report for Build 2b7063e7-43b1-4bfb-8314-d3471ed66c52

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.818%

---

Totals
Change from base Build 8421a20c-8cfe-4694-b0a7-b80f916cb093:	0.0%
Covered Lines:	4922
Relevant Lines:	5191

---

💛 - Coveralls

[nikxco]

I'm using NestJS 10.0.0 and still having the same issue.
Following is my app module where i'm using yup to validate my environment variables which is working fine except the ValidationError doesn't have all the information.

app.module.ts

  imports: [
    ConfigModule.forRoot({
      isGlobal: true,
      cache: false
      expandVariables: true,
      envFilePath: ['./env/.env.local', './env/.env.database'],
      load: [databaseConfig, appConfig],
      validationSchema: EnvironmentVariableSchema,
      validationOptions: {
        abortEarly: false,
      },
    }),
    MongooseModule.forRootAsync({
      useFactory: async (configService: ConfigService) => ({
        dbName: configService.get<string>('database.name'),
        uri: configService.get<string>('database.uri'),
      }),
      inject: [ConfigService],
    }),
    UsersModule,
    DatabaseModule,
    VerificationsModule,
    SubscriptionsModule,
    JobsModule,
    ResumesModule,
    LocationsModule,
    LanguagesModule,
    AlertsModule,
    CampaignsModule,
    CategoriesModule,
    CompaniesModule,
    CoursesModule,
    CreditsModule,
    CurrenciesModule,
    DesignationsModule,
    InsightsModule,
    InstitutionsModule,
    NextAuthModule,
    NotificationsModule,
    OpenaiModule,
    ReportsModule,
    RewardsModule,
    TagsModule,
  ],
  controllers: [AppController],
  providers: [
    AppService,
    { provide: 'APP_NAME', useValue: 'NestJS' },
    { provide: 'APP_VERSION', useValue: '1.0.0' },
    { provide: 'APP_GUARD', useClass: ApiKeyGuard },
  ],
})
export class AppModule {}

main.ts file

async function bootstrap() {
  const logger = new Logger('Bootstrap');
  const app = await NestFactory.create(AppModule, { abortOnError: false });
  const configService = app.get(ConfigService);
  const PORT = configService.get('app.apiPort', 3000);
  app.setGlobalPrefix('v1');
  app.useGlobalInterceptors(new LoggingInterceptor());
  app.useGlobalFilters(new MongoExceptionFilter());
  await app.listen(PORT);
  logger.log(`Application is running on: http://localhost:${PORT}`);
}
bootstrap().catch((error) => {
    /******This catch block never gets executed.*******/
    console.error('Error in bootstrap++++++++++++++++++++++++', error);
  });

I want to log bootstrap errors to an external system and in order to do so I must be able to to catch those errors explicitly.

Am I missing something here?? Please help me with this. @kamilmysliwiec