ladjs / dotenv-parse-variables Goto Github PK

https://github.com/niftylettuce/dotenv-parse-variables/blob/abd9a9f7499e6b09a8bd85435cfda84fe95937b3/src/index.js#L58-L61

Looks like inline comments in .env aren't handled?

e.g a .env containing the following:

LIMITER_MAX_CALL=50 # limit number of calls to this value per LIMITER_TIME_INTERVAL

returns in env

{
  ...
  LIMITER_MAX_CALL="50 # limit number of calls to this value per LIMITER_TIME_INTERVAL"
  ...
}

Ideally everything from "#" onward should be stripped when parsing.

If my .env has a variable that should be a string, but consists only of digits:

AWS_ACCESS_KEY_ID="123"

It will get parsed to number. How may I precent this? Are the quotation marks ignored?

Have you considered supporting parsing objects?

e.g. SOME_VARIABLE={"test": "hello"}, currently, we get SOME_VARIABLE: '{"test": "hello"}', but since that string is JSON parsible, would be nice to parse it into an object.

What's wrong with boolean parse?

require('dotenv').load();

const dotenvParseVariables = require('dotenv-parse-variables');

console.log(process.env);
process.env = dotenvParseVariables(process.env);
console.log(process.env);

result:

{
  "DEV": "true",
  "WWW": "http://localhost:3000",
  "PORT": "3000",
  "MONGODB_DSN": "mongodb://127.0.0.1/test",
  "MONGODB_DEBUG": "true"
}

{
  "DEV": "true",
  "WWW": "http://localhost:3000",
  "PORT": "3000",
  "MONGODB_DSN": "mongodb://127.0.0.1/test",
  "MONGODB_DEBUG": "true"
}

Currently when creating an array with just one item, it creates an array of two:

CORS_ORIGINS=myurl.com,
=> ['myurl.com', '']

It would be nice to be able to create an array even if there is just one item.

I'm probably doing something really wrong, but i can't find what...

import dotenv from 'dotenv'
import dotenvParseVariables from 'dotenv-parse-variables'

let env = dotenv.config()
if (env.error || !env.parsed) throw env.error
env = dotenvParseVariables(env.parsed, { assignToProcessEnv: true, overrideProcessEnv: true })
console.log(process.env)

My .env file:

PORT=3000
JWT_SECRET=token

What I got from process.env:

{
  PORT: '3000', // String
  JWT_SECRET: 'token'
}

What I expect:

{
  PORT: 3000, // Number
  JWT_SECRET: 'clinica'
}

What I'm doing wrong?

I have a token to access a third party API. This token contains a comma ",". In my .env file the token is saved as:

TOKEN=abcde,fghij

When I parse the .env variables with dotenv-parse-variables, the token is parsed as an array, e.g.
['abcde', 'fghij'] But of course I just want a string. Is this possible? Also with an asterisk, I am not able to get the desired result. Can you please help me?

Great library!

I'm using this with react-native-config, which includes a helper function in its configuration object. This function must first be manually stripped before passing the config to dotenv-parse-variables, otherwise it will throw an error: TypeError: value.indexOf is not a function.

As a convenience, it would be great if dotenv-parse-variables ignored any functions in the object being parsed.

Thanks!

Describe the bug

Node.js version: 20

Description: Big numbers like "12345678901234567" are parsed incorrectly to number

Actual behavior

"12345678901234567" becomes 12345678901234568 (number)

Expected behavior

"12345678901234567" becomes 12345678901234567 (bigint)

or

"12345678901234567" stays as "12345678901234567" (string)

Code to reproduce

.env:
ENV_VAR="12345678901234567"

Checklist

• I have searched through GitHub issues for similar issues.
• I have completely read through the README and documentation.
• I have tested my code with the latest version of Node.js and this package and confirmed it is still not working.

Not relevant to this lib

Is there a quick way to add the parsed variables to process.env, or do I have to create my own solution?

The README gives an example with console.log(process.env); which outputs type-casted variables e.g. BAZ: 2 vs BAZ: '2'.

This is not the case - any variable written back to process.env will be output as a string, and it does not appear possible to set and then read a type-casted variable from process.env.

The assignToProcessEnv and overrideProcessEnv work, they set the value to process.env as per the logic, but the type is lost.

You need to use the output of dotenvExtended.load() to see the type-casted variables, however this does not contain anything existing from process.env - so there is no place to get an entire process.env variable list with type-cast.

The way i have achieved this is by passing a copy of process.env into the package e.g.

const loadedDotEnv = dotenvExtended.load({
  silent: false,
  errorOnMissing: true
});
const env = require('dotenv-parse-variables')(Object.assign({}, process.env));

console.log(env);