Permission errors on Windows

[MetaMmodern]

Hi!

Your library works strange and requires access to neighbour users folder!!!

The error occures here: \src\env\env.ts:14:23

Red line means my user, and green arrow means another Windows user.

Moreover, the same ine caused an error yesterday, but that time it tried to access my own user root folder.

Are you sure that we need that strange logic for dotenv support?

Add a bug label please.

[hiro5id]

I'm just noticing this ticket now. I'll take a look tomorrow and i'll let you know what I find out.

[hiro5id]

@MetaMmodern I think I know what this has to do with. There is this feature where you can specify some environment variables either in .env file or in normal environment variables, to control different behaviour of the logger. For example you can tell it to not log time stamp.

When it looks for the optional .env file it walks up the tree trying to find one.

I believe you are experiencing a side effect of that action of looking for the .env file.

I will test this on a windows machine, I'm typically using Linux and Mac for my daily work.

In the mean time, do you have a different suggestion for the .env file searching mechanism?

It could be that it is walking up the tree and then inadvertently going too far and blundering into another user's folder somehow. But I need to pull out a Windows machine to see.

[hiro5id]

hey @MetaMmodern could you try version 2.7.0 ? I have disabled the recursive walking of up the tree looking for .env files... It now only looks in the current directory of the executing process.

[MetaMmodern]

hey @MetaMmodern could you try version 2.7.0 ? I have disabled the recursive walking of up the tree looking for .env files... It now only looks in the current directory of the executing process.

Hi. Okay, I'll check it asap, but maybe you'd better use something like app-root-path to use find the fe only in project folder.

[MetaMmodern]

@MetaMmodern I think I know what this has to do with. There is this feature where you can specify some environment variables either in .env file or in normal environment variables, to control different behaviour of the logger. For example you can tell it to not log time stamp.

When it looks for the optional .env file it walks up the tree trying to find one.

I believe you are experiencing a side effect of that action of looking for the .env file.

I will test this on a windows machine, I'm typically using Linux and Mac for my daily work.

In the mean time, do you have a different suggestion for the .env file searching mechanism?

It could be that it is walking up the tree and then inadvertently going too far and blundering into another user's folder somehow. But I need to pull out a Windows machine to see.

Sorry, didn't see this comment.
I think it woild be cool to have a *.config.json file instead of env. We've made such in our project. And as I mentioned you could use some third larty lib do determine the root folder of project and search for config file only there and not in higher folders.