Support absolute paths with the --env-file CLI option.

[virtuallyunknown]

What is the problem this feature will solve?

Well, the problem is really simple. Right now when you pass a file to --env-file such as:

node --env-file=.env

It will load correctly, provided you have a file called .env relative to the current working directory (as stated in the documentation).

However, if you call the command with an absolute path such as:

node --env-file=/home/user/some/path/.env

It will throw an error, even if the file exists:

node: /home/user/some/path/.env: not found

What is the feature you are proposing to solve the problem?

I propose that passing an absolute path to --env-file would detect it as such and try to load the file. Also, the current error message could be improved.

Supporting absolute paths might sounds like a niche feature, but it can be very useful in the context of mono-repositories.

What alternatives have you considered?

No response

[anonrig]

Support for absolute paths are already landed in main and will be included in the next release.

Ref: #51425

[virtuallyunknown]

Support for absolute paths are already landed in main and will be included in the next release.

Ref: #51425

Oh, I apologize. Should've researched more thoroughly before opening an issue, my bad.

But also cheers for implementing the feature!