Nest: Express set

[underfisk]

Bug Report

Current behavior

set is not being exposed in order to add custom config to express such as trust proxy

Input Code

const your = (code) => here;

Expected behavior

Being able to set express config such as trust proxy, views etc

Possible Solution

Environment

Nest version: X.Y.Z


For Tooling issues:
- Node version: XX  
- Platform:  

Others:

[kamilmysliwiec]

See this https://docs.nestjs.com/first-steps#platform

const app = await NestFactory.create<NestExpressApplication>(ApplicationModule);

[underfisk]

Hi what i mean is this:
https://expressjs.com/en/4x/api.html#app.set

[ricardosaracino]

This seems to work.. not sure if this is recommended

const server = express();

server.set('trust proxy', 1);

const app = await NestFactory.create(AppModule, new ExpressAdapter(server), {
    logger,
    httpsOptions: environment.httpsOptions,
});

[underfisk]

That's strange because the old nestjs version had set, now it's not exposed and it's very useful for this like trust proxy

[ricardosaracino]

Nest should not be dependent on express.. It makes total sense

[underfisk]

Yes but since nest uses mainly it and set is one of the most used things, there's no problem on exposing it that's what i mean

[ricardosaracino]

Gonna have to agree to disagree on this one 😉

[kamilmysliwiec]

There is a set method, but you have to use NestExpressApplication interface. See here https://docs.nestjs.com/first-steps#platform

const app = await NestFactory.create<NestExpressApplication>(ApplicationModule);
app.set(...)

[ricardosaracino]

this is much better than what im doing

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.