The features section in the docs states that nodemon is available in the project, when it's clearly not. It's not added as a dependency or as a command in the project. Maybe remove this from the docs or actually add nodemon?

Hello, I have tested to install on a fresh expo sdk 36 blank project the example :

 npm install react-native-dotenv metro-react-native-babel-preset --save-dev

I have created a .env file with:

API_KEY=lorem
ANOTHER_CONFIG=foobar

I edited babel.config.js with:

module.exports = function(api) {
  api.cache(true);
  return {
-    presets: ['babel-pr

Hello,

Trying to run the WSGI example on readme doesn't work when runned in any other folder than the one the .env lives.

For example, having a folder with a .env a file named main.py:

import os
import dotenv

print("Loading file:", os.path.join(os.path.dirname(os.path.dirname(__file__)), '.env'))
dotenv.read_dotenv(os.path.join(os.path.dirname(os.path.dirname(__file__)), '

• start reporting on coverage (somehow...)

Issue type:

• question
• bug report
• feature request
• documentation issue

nestjs-config version

@nestjs/common+core or other package versions

• @nestjs/common:
• @nestjs/core:

Excepted behavior

I want to be able to use strict typing within my service. Using `config.get('something'

What problem does this feature solve?

In most places where dotenv is used system env vars override the dotenv vars, however dotenv-module does the exact opposite, swapping this around would give the expected result when using systemvars: true

Right now the message looks like this:

.env:2 The FOO-BAR key should go before the FOO-BAR key

Need to add the check name to the message:

.env:2 UnorderedKey: The FOO-BAR key should go before the FOO-BAR key

Related wemake-services/wemake-python-styleguide#1221

According to the documentation for createRedirect, some plugins support the non-standard redirect parameters force and statusCode. It might be nice for us to support these too.

With Redirection Rules, we can support force by adding/removing the HttpErrorCodeReturnedEquals: '404' condition. We can support statusCode by overriding