-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where are the docs? #75
Comments
The documentation is not yet published |
I tried to use the built in help command instead, however I hit a roadblock when generating a new module.
I tried different paths because I wasn't sure what base path it would try to use. Any idea what I am doing wrong? With the stable 3.x version I had the same issue, which had been closed here: #61 . Apparently it hasn't been fixed by the rewrite unless I am doing something wrong? |
seems to be the module import that cause this issue... |
Can't reproduce the bug on a VM with Windows 10 version... |
The app.module.ts: import { HelmetMiddleware } from '@nest-middlewares/helmet';
import { MiddlewaresConsumer, Module, RequestMethod } from '@nestjs/common';
import { ConfigModule } from './common/config/config.module';
import { AuthMiddleware } from './middlewares/auth/auth-middleware';
import { AuthService } from './middlewares/auth/auth.service';
import { JwtStrategy } from './middlewares/auth/passport/jwt.strategy';
import { PlayersModule } from './routes/players/players.module';
@Module({
imports: [ConfigModule, PlayersModule],
controllers: [],
components: [AuthService, JwtStrategy]
})
export class AppModule {
public configure(consumer: MiddlewaresConsumer): void {
consumer
.apply(HelmetMiddleware)
.forRoutes({ path: '*', method: RequestMethod.GET })
.apply(AuthMiddleware)
.forRoutes({ path: '*', method: RequestMethod.GET });
}
} |
Test written to check what happens ! |
Try to release today to enjoy the cli with the fix ;-) |
Please upgrade to 4.0.0 or 5.0.0 depends on the Nestjs major version you want to use |
The readme says one should check the nestjs documentation regarding the usage, but I couldn't find anything related to nest-cli usage in there.
Am I missing something?
The text was updated successfully, but these errors were encountered: