Micael Levi L. Cavalcante
Micael Levi L. Cavalcante
another guide on this topic: [Advanced NestJS: How to build completely dynamic NestJS modules](https://dev.to/nestjs/advanced-nestjs-how-to-build-completely-dynamic-nestjs-modules-1370)
@Tony133 can you take this PR to add another minor note regarding the `ConfigModule`? background: people may not know that env. vars coming from the runtime environment takes precedence over...
for reference: https://github.com/nestjs/awesome-nestjs
To create a bare minimum NestJS standard app (ie., express HTTP server; with no test runner, no linter, etc) from scratch: https://gist.github.com/micalevisk/68c44347bb79344e4f3bce81c6450396
```js .overrideProvider(CACHE_MODULE_OPTIONS) // exported from @nestjs/common .useValue(newCacheModuleOptions) ``` might help you.
@binarytracer that will be fixed by https://github.com/nestjs/nest/pull/10143
in v9 you can use `app = moduleFixture.createNestApplication({ bodyParser: false });` which is intuitive. so I believe there's no need to document that in the docs website anymore.
I guess we can close this now :smiley_cat: unless you think we need to update v8 docs
hi @silto do you think that we should update v8 docs?
@sethew I guess you could ask this on https://discord.gg/nestjs