⚠️ Potential issue

Resolve the duplicate PORT key conflict.

You define PORT twice with different values (3000 and 8000). Most environment parsers handle this by using the last occurrence, making PORT=8000 the effective value. This creates unpredictable behavior and potential debugging challenges.

Consider removing one of the duplicate definitions or using descriptive names:

-PORT=3000
-PORT=8000
+DEV_PORT=3000
+PROD_PORT=8000

In dot-env/test.env at lines 1 to 2, there are duplicate definitions of the PORT
key with different values (3000 and 8000), which can cause unpredictable
behavior. To fix this, remove one of the duplicate PORT entries or rename one of
them to a more descriptive key to avoid conflicts and ensure clarity in
environment configuration.

⚠️ Potential issue

Fix the missing equals sign in environment variable assignment.

The DB_URL line lacks an equals sign, making it an invalid environment variable declaration. Most parsers will ignore this line entirely or treat it as malformed.

Apply this fix:

-DB_URL postgres://localhost
+DB_URL=postgres://localhost

In dot-env/test.env at line 3, the environment variable assignment for DB_URL is
missing an equals sign. Fix this by adding an equals sign between the variable
name and its value, changing the line to "DB_URL=postgres://localhost" to ensure
it is a valid environment variable declaration.

⚠️ Potential issue

Remove the leading space before the variable name.

The SECRET_KEY line starts with a space, which creates an invalid variable name. Environment parsers typically require variable names to start at the beginning of the line without leading whitespace.

Apply this fix:

- SECRET_KEY=12345
+SECRET_KEY=12345

In dot-env/test.env at line 4, remove the leading space before the SECRET_KEY
variable name to ensure it starts at the beginning of the line, making the
environment variable valid and parsable.

⚠️ Potential issue

Provide a valid key-value pair format.

Line 5 contains "UNQUOTED VALUE" without an associated variable name or equals sign. This creates an invalid environment variable entry that parsers cannot process.

Specify a proper key-value format:

-UNQUOTED VALUE
+SOME_KEY=UNQUOTED VALUE

Or if this represents a comment, prefix it with a hash:

-UNQUOTED VALUE
+# UNQUOTED VALUE

In dot-env/test.env at line 5, the entry "UNQUOTED VALUE" is invalid because it
lacks a key and equals sign. Replace it with a valid key-value pair using the
format KEY=VALUE, or if it is meant to be a comment, prefix the line with a hash
(#) to make it a comment.