Example:

# .env
test

Actual behavior:

If we run dotenv-linter against a .env file with the test key, we will see only one warning:

$ dotenv-linter .env
Checking .env
.env:1 KeyWithoutValue: The test key should be with a value or have an equal sign

Found 1 problem

If we fix that file and run check again, we will see another warning:

$ 

• start reporting on coverage (somehow...)

We need to enforce \n for line breaks.

Currently, in the gatsby-plugin-s3 configuration, I'm not finding a way to set the s3ForcePathStyle option. This is necessary in cases, where S3-Compliant Object Storage Services, which might not be AWS have this path style. Some examples could be Minio

https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html#s3ForcePathStyle-property

Would be happy to send a